In a message dated 4/14/2001 12:04:43 AM Eastern Daylight Time, [EMAIL PROTECTED] writes: > What do people think? I'd be willing to take the diff and apply > it to 4.0 if the community thinks its worthwhile/safe. > > - Dossy > > > On 2001.04.13, Mr. Source Forge <[EMAIL PROTECTED]> wrote: > > Support Requests item #416028, was updated on 2001-04-13 14:49 > > You can respond by visiting: > > http://sourceforge.net/tracker/?func=detail&atid=203152&aid=416028&; > group_id=3152 > > > > Category: None > > Group: None > > Status: Open > > Priority: 5 > > Submitted By: Adam Zell (zellster) > > Assigned to: Nobody/Anonymous (nobody) > > Summary: WInsock2 > > > > Initial Comment: > > Moving Windows-specific networking code to use Windows > > Sockets 2.0 is a good thing, as it allows things like > > scatter/gather IO with WSASend, WSARecv, etc. > > > > I have made the changes necessary, and it seems to > > work. The bulk of the changes are changing includes > > from <winsock.h> to <winsock2.h>, and changing > > references to wsock32.{dll,lib} to ws2_32.{dll, lib}. > > Hello, The socket-driver architecture of aolserver makes it hard to implement scatter/gather i/o in a clean way without breaking the API for both Unix and Win32. I'd like to release 4.0 soon so folks can try out the new features (better internationalization, virtual servers, tcl8.3.3 only, few others goodies) and then focus on optimizing i/o in the 4.1 release. So, how about we put the ws2 stuff in then? -Jim
