WININET: move to Windows sockets

Alexandre Julliard julliard at winehq.org
Mon Apr 5 12:24:20 CDT 2004


Hans Leidekker <hans at it.vu.nl> writes:

> So, is this a problem? Depends on what's important to you, but I'd
> argue that it's more important for Wine to open up wininet (and
> consequently winsock) to more users and developers. That may eventually
> attract more developers to fix bugs or even the performance issues
> with our implementation.

There's no real reason that we cannot use Unix sockets on Unix and
Windows socket on Reactos with the same code, it just needs a bit of
header magic; and this will be useful for Winelib apps too.

> By the way, 100 *asynchronous* HTTP GETs in a tight loop will reliably
> crash Wine, both with Unix sockets and Windows sockets.

Yep, wininet is not really thread-safe at this point.

-- 
Alexandre Julliard
julliard at winehq.org



More information about the wine-devel mailing list