[EXPERIMENTAL PATCH]: Winsock2
andi at rhlx01.fht-esslingen.de
Wed Nov 7 13:50:11 CST 2001
On Wed, Nov 07, 2001 at 10:54:02AM -0800, Francois Gouget wrote:
> * To answer your question:
> /* Code copied largely from WSOCK32_accept() */
> /* FIXME: Can we simply call WSOCK32_accept() instead ? */
> /* I wasn't sure because of the AsyncSelect stuff at the end,
> which presumably should only be called if the connection is accepted */
> Winsock2 should not call the wsock32 library. It should be the
> opposite. One of the things on my todo list (but whether I will have
> time to actually do it is another matter) is to reorganize the winsock
> libraries so that wsock32 and winsock are together in dlls/wsock32. The
> reason is that they both implement the winsock1 API except one is 16bit
> and the other 32bits. Then in dlls/winsock we would be left with just
> ws2_32 which implements the winsock2 API. So having ws2_32 call to
> wsock32 is not going in the right direction :-)
Sorry, but this directory stuff sounds rather dainbread to me.
IMHO winsock/wsock32 should be in winsock/, and ws2_32 should be in winsock2/
Or, maybe even better, use winsock1/ instead of winsock/.
WTH would you want to do it in a different way ?
Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany
Tel. +49 7159 800604 http://home.nexgo.de/andi.mohr/
More information about the wine-devel