> Sounds interesting...what about writing data to the socket? Hmm.
If an overlapped write is issued upon a IOCP'd socket, the callback function will be called when that write has completed. If I add a function to the API through which overlapped writes are issued, it will be possible to tell if a write has completed or if a read has completed (e.g. the event type will be useful and correct) with a negligable overhead (e.g. no memory allocation, just trivial stuff). This would mean that all socket I/O would occur through a single function, the callback function. It would switch on the event, the user receives the socket and the event that has occured, and, accordingly to earlier discussion, very large numbers of sockets can so be handled. _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users
