Bart Smaalders writes: > Kacheong Poon wrote: > Define a new asynchronous call similar to lio_listio that permits > the collection of struct sockaddr & socklen_t info. This would > then generate async io completion events, which could be retrieved > via an event port once the IO had completed.
This seems reasonable to me, but I think the error semantics have to be worked out _very_ carefully. The sendfile/sendfilev fiasco gives a pretty good cautionary tale. As for making it sockets-only, I'd be worried that application programmers would be sufficiently constrained that they would end up being unable to use the resulting interface. Every time we've tried to come up with one of these special new interfaces, the first question asked is, "great, but my polling loop code is currently pretty generic, so how do I get <STREAMS, character devices, other I/O> into this interface?" -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list networking-discuss@opensolaris.org
