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

2010-09-22 Thread Mike Kaplinskiy
On Wed, Sep 22, 2010 at 6:13 PM, James Mckenzie wrote: > > > > -Original Message- >>From: Ricardo Filipe >>Sent: Sep 22, 2010 1:18 PM >>To: wine-devel@winehq.org >>Subject: Re: ws2_32: implement AcceptEx and GetAcceptExSockaddrs (try 3) >> >&g

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

2010-09-22 Thread James Mckenzie
-Original Message- >From: Ricardo Filipe >Sent: Sep 22, 2010 1:18 PM >To: wine-devel@winehq.org >Subject: Re: ws2_32: implement AcceptEx and GetAcceptExSockaddrs (try 3) > >2010/9/21 Mike Kaplinskiy : >> Thanks for the feedback Alexandre. The complexity of the

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

2010-09-22 Thread 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 >> wo

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

2010-09-22 Thread 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