From owner-freebsd-stable Thu Mar 29 13:20:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 9B89837B71C for ; Thu, 29 Mar 2001 13:20:45 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA11918; Thu, 29 Mar 2001 16:19:47 -0500 (EST) Date: Thu, 29 Mar 2001 16:19:47 -0500 (EST) From: Daniel Eischen To: Nate Williams Cc: Brian Matthews , "'nate@yogotech.com'" , freebsd-stable@FreeBSD.ORG Subject: RE: Threads vs. blocking sockets In-Reply-To: <15043.40533.488134.203176@nomad.yogotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Mar 2001, Nate Williams wrote: > > | 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). This thread has gotten rather large, and I'm picking a random message in which to reply... We should be able to easily make the threads library wait for all the data to be read or sent to blocking file descriptors. Perhaps this should go to -arch for discussion. I don't really care one way or the other, but I can change the current behaviour if necessary. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message