Subject: Re: FIONWRITE proposal
To: None <email@example.com>
From: Bill Studenmund <firstname.lastname@example.org>
Date: 10/20/2004 15:24:29
Content-Type: text/plain; charset=us-ascii
On Thu, Oct 14, 2004 at 07:38:34AM -0400, Allen Briggs wrote:
> On Wed, Oct 13, 2004 at 09:13:25PM -0700, email@example.com wrote:
> > Given that the interface exists and has a particular meaning already,
> > I'd follow that.
> FWIW, I agree with this, although the manual should be explicit that
> it doesn't match what you might expect if you're familiar with the
> semantics of FIONREAD. With no prior art, it would make the most
> sense to have:
I plan on beefing up the man entry. I'll also add FIONSPACE.
> Given the prior art, however, we should probably match the existing
> semantics. Does anyone other than vxworks define it?
Kinda. Linux extends TIOCOUTQ functionality to sockets, so they=20
essentially have this functionality, just under a different name.
I much prefer FIONWRITE to TIOCOUTQ. While FIONOUTQ would make sense,=20
there already is prior art for FIONWRITE.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----