On 4/23/07, Anders Persson <[EMAIL PROTECTED]> wrote:
I just published a design document for the kernel sockets interface[1]. The document is short, so hopefully everyone will have time to read it :) Any comments would be appreciated.
Few things... - Are these sockets goind to obey 3SOCKET or 3XNET semantics? - I think the ksocket_t * should be the last arg. to ksock_socket(). In general my preference is for value-return args. to be at the end of the list. - Is ksock_set_nonblocking() necessary? Could this not be handled by an option passed to ksock_setsockopt()? - I think the ksock_callback_t passed to ksock_accept() is slightly confusing. Is it really necessary for an accepted socket to immediately have callbacks? It would be more straightforward if the thread calling ksock_accept() simply called ksock_callback() upon its return. Paul -- Paul Durrant http://www.linkedin.com/in/pdurrant _______________________________________________ networking-discuss mailing list [email protected]
