471,344 Members | 1,423 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,344 software developers and data experts.

long delay sending via tcpip socket in .NET

Hi,
I have a connection which after an initial handshake has one way traffic.
I am sending bursty data. When I write a data buffer (variable size) the
last portion of it is not sent to the server until I start writing the next
buffer which may be 1/2/10/20/30 seconds later. Im using NetworkStream which
says it's unbuffered and Flush() is a no op. When I know I may not be sending
more data for a while how can I ensure that my data is flushed immediately?
The connection can not be closed (server constraint).
thanks,
-john

Aug 3 '05 #1
2 2189
hi john. sorry but this isnt a solution to your problem. i was wondering if
you had solved this problem or found a work around? i have been all over the
place finding a way to fix this with my program and you are the first person
to mention the same exact problem im going through.

"John Lemire" wrote:
Hi,
I have a connection which after an initial handshake has one way traffic.
I am sending bursty data. When I write a data buffer (variable size) the
last portion of it is not sent to the server until I start writing the next
buffer which may be 1/2/10/20/30 seconds later. Im using NetworkStream which
says it's unbuffered and Flush() is a no op. When I know I may not be sending
more data for a while how can I ensure that my data is flushed immediately?
The connection can not be closed (server constraint).
thanks,
-john

Oct 26 '05 #2
No unfortunately I didnt get any responses and I had to back burner this as
it was a startup time only problem and I had bigger issues to move on to. It
still take me 6-8 seconds to go through my little backand forth handshake
protocol before my comms are open for business. Maybe someday I'll get a
change to re-investigate this. Good luck and post if you figure it out in
the mean time :-)

"Kelly Morphis" wrote:
hi john. sorry but this isnt a solution to your problem. i was wondering if
you had solved this problem or found a work around? i have been all over the
place finding a way to fix this with my program and you are the first person
to mention the same exact problem im going through.

"John Lemire" wrote:
Hi,
I have a connection which after an initial handshake has one way traffic.
I am sending bursty data. When I write a data buffer (variable size) the
last portion of it is not sent to the server until I start writing the next
buffer which may be 1/2/10/20/30 seconds later. Im using NetworkStream which
says it's unbuffered and Flush() is a no op. When I know I may not be sending
more data for a while how can I ensure that my data is flushed immediately?
The connection can not be closed (server constraint).
thanks,
-john

Oct 27 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

9 posts views Thread by Brian Roberts | last post: by
2 posts views Thread by John Lemire | last post: by
18 posts views Thread by Larry Herbinaux | last post: by
3 posts views Thread by TulasiKumar | last post: by
1 post views Thread by CKane | last post: by
9 posts views Thread by =?Utf-8?B?U2hhdW5P?= | last post: by
reply views Thread by Ronak mishra | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.