|
From: David G. <dav...@po...> - 2008-12-07 10:55:40
|
Just a happy announcement that tip-162-branch in CVS is building and working on windows: E:\tcl_ws\tcl_tip162\win>release_vc8\tclsh86 % set s [socket -type tcp6 www.kame.net 80] sock672 % fconfigure $s -sockname 2001:470:1f04:ed::2 davygrvy-pt.tunnel.tserv3.fmt2.ipv6.he.net 3182 % fconfigure $s -peername 2001:200:0:8002:203:47ff:fea5:3085 orange.kame.net 80 The old Win3.11 WSAAsyncSelect based I/O notification method is now gone. In it's place is a more modern and scalable use of overlapped sockets using completion port notification. The code base it came from has a good history of being stable. http://technet.microsoft.com/en-us/sysinternals/bb963891.aspx A non-NT based implementation using WSAEventSelect has yet to be invented. In the meantime, I'm thinking of using the old code as a runtime fallback if needed. Hopefully by Christmas I'll have it all polished. I've started skeletal implementations of IrDA and Bluetooth additions mainly to force me to consider what the best API changes are needed so that we don't have to revisit API changes again. Whether the new protocols make it to 8.6 or not is not my short term goal. I've also started a UDP section of the code in the hopes that one day we might fill it and turn it on. An asynchronous and protocol agnostic resolver is also in the works. That's about it for my dream networked Tcl.. Is it your's too? |