[Libevent-users] Add support for WINDOWS Overlapped IO

[Zhu Han]

Toby,

Good work!

There is several questions for your implementation:

1) If you play with the Completion port, there is no reason to use the
hEvent  in the OVERLAPPED structure. Why do you use it?

2)I suppose socket_internal_iocp_read is called before you invoke the
callback to let the callback consume the received data. Why do you call
socket_internal_iocp_read firstly?

3)Is there any plan to support all of the Async operations, such as connect,
listen, accept, read and write?

BTW: your implementation has a lot of difference with libevent. The most
important one is libevent is a "single-threaded event-driven" library. This
could relieve the programmer from the burden of explicitly synchronization,
althouth it can't explore the capability of SMP.

best regards,
hanzhu
On 12/10/06, Toby Douglass <toby.douglass at summerblue.net> wrote:
>
> Zhu Han wrote:
> > I'm afraid WINDOWS Overlapped IO is a critical feature for libevent
> because
> > some of the servers required it.  I try to implement  this feature with
> > Completion Port.  Is anyone  busing on  it? If not, I will try to do it.
>
>
> I've written an IOCP library, which is here;
>
> http://www.summerblue.net/computing/libiocp/index.html
>
> It's not integrated into libevent though, which is something I'm not
> doing.
>
> I've finished rewriting that IOCP library to support listen sockets, so
> the IOCP stuff will take care of all the accept behaviour, too.  Right
> now I'm writing up test/example code for that, once it tests okay, I'll
> release, which I expect to do next weekend.
>
> _______________________________________________
> Libevent-users mailing list
> Libevent-users at monkey.org
> http://monkey.org/mailman/listinfo/libevent-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://monkeymail.org/archives/libevent-users/attachments/20061210/80817ae9/attachment.htm