I am using CAsyncSocket to communicate between two instances of an
application. This works OK provided the message length is <4k bytes. From
using GetSockOpt the Socket Send and Receive buffers appear to be set to
8k
bytes. I have tried increasing this to 16kbytes using SetSockOpt but this
has
no effect on the problem.
Without a description of the problem I can only guess what might be
going wrong.
Does you receiver code expect to receive a whole message in one go ?
If so that's the problem.
Is there also some underlying limit built in to the communication
channels?
No.
I am using Windows XP, Visual Studio 6 and TCP/IP protocol
Boatprog
Re: Sockets. Limit on message length. ... using GetSockOpt the Socket Send and Receive buffers appear to be set to ...Boatprog... (microsoft.public.win32.programmer.networks)
Re: Sockets debugging tools ... This is perfectly possible by programming your peer not ...system buffers are fairly large ... and the socket just remains in a permanent would-block state? ... > returned by recv or send calls. ... (comp.unix.programmer)
Re: Socket switch delay ...buffers are queued and will be later sent. ...socket, not sure about a blocking socket. ... >>(and I noticed you don't do overlapped receive at the server!) ... > optional in the client too). ... (microsoft.public.win32.programmer.networks)
Re: Automatic TCP send socker buffer sizing ... I've seen in production that some sockets get large very quickly during periods of high latency (eg: when sending to a user downloading from a cablemodem and their headend gets temporarily saturated and has large buffers, which raises the RTT under saturation, which increases the bandwidth delay product), but then as there isn't any code to shrink the buffers. ... This would probably need to be in the timers to notice the case of the sender temporarily stopping sending - eg in a keepalive http socket... Perhaps we can have a new setsockopt() flag to disable automatic sizing on a socket if we have a specific size we want a buffer to be and don't want it dynamically sized. ... (freebsd-net)
