Date: Thu, 29 Mar 2001 10:44:36 -0700 (MST) From: Nate Williams <nate@yogotech.com> To: Brian Matthews <blm@actzero.com> Cc: "'freebsd-stable@freebsd.org'" <freebsd-stable@FreeBSD.ORG> Subject: Re: Threads vs. blocking sockets Message-ID: <15043.29828.704595.42066@nomad.yogotech.com> In-Reply-To: <F0D64494733BD411BB9A00D0B74A0264021C9B@cpe-24-221-167-196.ca.sprintbbd.net> References: <F0D64494733BD411BB9A00D0B74A0264021C9B@cpe-24-221-167-196.ca.sprintbbd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> However, I would then expect the threaded versions of the data > transfer calls (send*, etc.) to loop over the actual system calls. Why? Do other OS's not require you to check your return values, to make sure that the call sent everything you expected it to? I believe FreeBSD is acting normally. If you want to send *all* the data, then you need to do your own checking to make sure everything is sent. This is 'expected' behavior. 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.29828.704595.42066>