darrenr wrote: > When I use SO_RCVBUF, I'm specifying a read buffer > size for data > to be read by my application. I would expect said > buffer to be used > for my data and not protocol headers. Same for > SO_SNDBUF. > This is the way it has worked ever since I started > programming TCP > client/server applications. If an operating system > were to decide > to do something else, I'd call that behaviour broken.
The issue with SO_SNDBUF/SO_RCVBUF is that there is no such "standard" as to what they ought to imply or what the underlying OS should or should not do with it; on some OSes out there the kernel caps the size of the buffer, i.e. what you get from getsockopt() may not be the same as what you have set earlier with setsockopt(). I'm not sure I'd call it broken. > As Brian put it in his email, this "feature" in > Solaris breaks applications > that have (and do) work flawlessly everywhere *but* > Solaris 10. Do you have examples of any such "real" applications? Adi > > Darren This message posted from opensolaris.org _______________________________________________ networking-discuss mailing list [email protected]
