--5vNYLRcllDrimb99
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 20, 2006 at 02:15:17PM +1100, Daniel Carosone wrote:
> On Sun, Mar 19, 2006 at 07:07:06PM -0800, Bill Studenmund wrote:
>=20
> > My question was if we want both iovec and non-iovec versions.
>=20
> I'm thinking a readx/writex that take an iovec and flags.
>=20
> Then all the previous interfaces can be implemented internally in
> terms of readx/writex (p/non-p as a flag, non-iovec as a
> single synthesised iovec, etc) if worthwhile.

Agreed.

> Worth thinking ahead of what other flags we might want, and what they
> might imply for the interface of the new iovec structure...

Just to be clear, I am not planning on changing the layout of struct=20
iovec. If someone else wants to do it/help me do it, that's fine.

Take care,

Bill

--5vNYLRcllDrimb99
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFEHtjOWz+3JHUci9cRAhcIAJ9mtOsgevUUw/Ez5KgcxWGcKQ4WHQCfQ7nF
Ycz62pnyRJYq6n5ui7DbyJk=
=Yy3r
-----END PGP SIGNATURE-----

--5vNYLRcllDrimb99--