Hello
I am developing an application that sometimes ends up sending a large
burst of data on the socket. My understanding is that the kernel will
drop queued data randomly if the Send Buffer is overwhelmed with data.
In order to prevent this there is the "SendBuffer" (One of the the
enumeration values in SocketOptionName -
http://msdn.microsoft.com/library/de...classtopic.asp
I have not been able to determine the largest possible value that
SendBuffer can be assigned; I really doubt if it is unlimited upto the
system memory.
I am hoping to get information about platforms running *WinXP* as well
as *CF* so I am placing the post on both the groups.
Extrapolating the question, *if* the SendBuffer is limited to a few
tens of kB then is there a built in queueing mechanism to make sure
that data trickles into the TCP connection when the burst comes? This
is a real-time app (with almost gaming like requirements) so I am not
sure if using a messaging queue would be very useful because the
messaging queue stores stuff on the hard-disk sometimes. Anyone had any
experience with these type of issues?
Thank you very much for reading.
-Jumu
Similar Threads
