couttsj

@Mikekan13: > Also how far along are you on yours? I had some trouble with the UDP part of it, but I believe it is ready for limited testing. Any volunteers? J.A. Coutts

@MrMiguu: > So the VB6 Winsock control basically makes controlling the Winsock API simple? I found an [article](http://vbcity.com/forums/p/27458/115174.aspx) that explained how to inject the Winsock 2 API into any VB6 application. Windows has used Winsock 2 since Windows 95\. However, only the newer versions of WS2_32.dll (version 6) contain the new calls necessary to support IPv6\. Version 5 included with XP SP2 does not. Dual stack IPv4/IPv6 is included with both Vista and Win 7, and can be enabled on XP SP2\. The only way to use IPv6 if you do not have access to IPv6 transport (which is 98% of us) is to use a tunnel broker. Microsoft provides the Teredo tunnel on Vista/Win7, which to the best of my knowledge is the only one that will work behind a NAT router. The Teredo tunnel is not enabled by default, but if you want instructions on enabling it, I can provide them. J.A. Coutts

@Mikekan13: > So how far along are you on yours? Far enough to get a simple TCP Chat server/client routine running in both IPv4 & IPv6, but I could use some help from an experienced socket programmer. J.A. Coutts

IMHO they are both equally as good. Emiliano based his work on the work done by Oleg Gdalevich, and added his own method of utilizing callbacks. I found Oleg's routines a little easier to follow, but Emiliano had better error routines. I used parts of both in building up my routines, as providing the same functionality as the Winsock Control was not the highest priority for me. Emiliano also went a little further in providing the code necessary to make a Control. A Control Array would be necessary when operating a multi-socket server, as each control only manages one socket. J.A. Coutts

You can try it in VBv4 right now: http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=69532&lngWId=1 by Oleg Gdalevich http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=52072&lngWId=1 By: Emiliano Scavuzzo VB6 doesn't do threading very well, so the use of callbacks is the only viable option. Each of the above authors take a slightly different approach to this, but both are drop-ins for the Microsoft Winsock Control. You will notice a performance improvement with either of them when you substitute in an existing application. J.A. Coutts

@MrMiguu: > **@couttsj** Are you doing this for VB6's Winsock object? Yes, I am modifying the cSocket Class, which is a drop-in replacement for the Microsoft Winsock Control.

VB6 is heavily dependent on COM (Common Object Model). Microsoft has long hinted that it would like to move away from COM, but it is so heavily ingrained in the operating system and in their other software that I would consider it suicidal (but not impossible). As far as Winsock is concerned, it is true that the Winsock Control does not support IPv6, and it doesn't look like it ever will. IPv6 is supported in Vista, Win 7, and XP-SP2\. Both Vista and Win 7 support the new calls required to support IPv6 via the library file "ws2_32.dll". Apparently this file can be added to XP-SP2 to provide the necessary support, but I have not tried it. The crux of this is that the Winsock API now supports IPv6 on these systems, and I am in the process of modifying the "cSocket" Class from Oleg Gdalevich to support IPv6\. This Class module and it's support module "modSocketMaster" are a direct drop-in replacement for the Winsock Control, but . This conversion is proving to be a lot more difficult than I anticipated. I have a simple TCP Chat program working in both IPv4 and IPv6, but there are still some fundamental differences in these 2 protocols that are causing difficulty. With IPv4, you only had one IP address to worry about, but with IPv6, you can have several (I currently have 4). The Winsock Control and the cSocket Class were both designed to support a single socket. If any VB6 programmers are willing to work with me to help make this transition, please contact me. J.A. Coutts