Date: Thu, 29 Mar 2001 13:43:01 -0700 (MST) From: Nate Williams <nate@yogotech.com> To: Brian Matthews <blm@actzero.com> Cc: "'nate@yogotech.com'" <nate@yogotech.com>, freebsd-stable@FreeBSD.ORG Subject: RE: Threads vs. blocking sockets Message-ID: <15043.40533.488134.203176@nomad.yogotech.com> In-Reply-To: <F0D64494733BD411BB9A00D0B74A0264021C9F@cpe-24-221-167-196.ca.sprintbbd.net> References: <F0D64494733BD411BB9A00D0B74A0264021C9F@cpe-24-221-167-196.ca.sprintbbd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> | Again, all threading libraries I've used (not just on > | FreeBSD) *require* > | the user to check that when sending/receiving data, the > | caller must make > | sure that all the expected data has been sent/received. > > Linux doesn't, and I don't think Solaris does (we just moved so I can't try > it now, but when I was investigating the problem I'm pretty sure I tried it > on our Sun box). Are you using non-blocking sockets, and are you using a user-space library on those OS's? (I suspect not, because when I last used Solaris it acted that way). Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15043.40533.488134.203176>