From: "Toby Douglass" <[EMAIL PROTECTED]>
I wrote:
> On a related note, did someone say that the event handle in the overlapped
> structure used by the IO functions (ReadFile, etc) is not actually used?
>
> If that's actually untouched, I could use it for my own purposes. The
> alternative is probably a malloc() per write operation :-/
As it is, it's easy to support serial writes with IOCP, it's supporting
multiple concurrent writes which is awkward for a convenient-to-use API
over IOCP - and this I would think is absolutely required for some uses of
UDP sockets.
I haven't tried any UDP async socket stuff, not with IOCPs nor anything.
Tell us how it goes! Still, I think I'm missing the point of multiple
concurrent writes - wouldn't the output be undefined?
--
felix: lightweight threads, HOFs and game scripting.
svn co https://svn.sourceforge.net/svnroot/felix/felix/trunk felix
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkey.org/mailman/listinfo/libevent-users
