Re: ws2_32: implement AcceptEx and GetAcceptExSockaddrs (try 3)

[Ricardo Filipe]

2010/9/21 Mike Kaplinskiy :
> Thanks for the feedback Alexandre. The complexity of the wine APC &
> I/O system never stops amazing me. Third time's the charm?
>
> try 3: correctly use an apc to free internal async structures (which
> would explain why we have the apc parameter...). Strangely moving
> SetEvent & AddCompletion to the apc makes it not work (...an exercise
> for another time)
> try 2: use the new async i/o callbacks
>
> dlls/ws2_32/socket.c     |  257 +++++++++++++++++++++++++++++++++++++++++++++-
>  dlls/ws2_32/tests/sock.c |   14 ++-
>  2 files changed, 263 insertions(+), 8 deletions(-)

thank you for the perseverence to make this possible in the main tree.

ws2_32: implement AcceptEx and GetAcceptExSockaddrs (try 3)

[Austin English]

On Wed, Sep 22, 2010 at 8:18 PM, Ricardo Filipe
 wrote:
> 2010/9/21 Mike Kaplinskiy :
> > Thanks for the feedback Alexandre. The complexity of the wine APC &
> > I/O system never stops amazing me. Third time's the charm?
> >
> > try 3: correctly use an apc to free internal async structures (which
> > would explain why we have the apc parameter...). Strangely moving
> > SetEvent & AddCompletion to the apc makes it not work (...an exercise
> > for another time)
> > try 2: use the new async i/o callbacks
> >
> > dlls/ws2_32/socket.c     |  257 +++++++++++++++++++++++++++++++++++++++++++++-
> >  dlls/ws2_32/tests/sock.c |   14 ++-
> >  2 files changed, 263 insertions(+), 8 deletions(-)
>
> thank you for the perseverence to make this possible in the main tree.

+1. Too bad it wasn't a 1.4 milestone, we'd have one ready to scratch
off the list :-).