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
