On Thu, May 20, 2010 at 7:42 PM, Arno Garrels <arno.garr...@gmx.de> wrote:

> Angus Robertson - Magenta Systems Ltd wrote:
> >> There's an option to dynamically load a different winsock version at
> >> runtime (see properties ReqVerHigh and ReqVerLow).
> >> However loading v2.x requires winsock2 headers, and if we want IPv6
> >> we must use winsock2 API. I think I'll keep these two properties as
> >> dummies, they would no longer work, what do you think?
> >
> > Yes, leave the version properties, but ignore them.
>
> Done:
>
> "TcpSrv (c) 1999-2008 by Fran├žois PIETTE. V7.02
>  TWSocket (c) 1996-2010 Francois Piette V7.39
>  TWSocketServer (c) 1999-2008 F. Piette V7.00
>  I am "asus"
>  IP: 2001:db8::3
> 192.168.178.200
> 192.168.135.1
> 192.168.239.1
>
> Waiting for clients...
> Client connected. Remote: 2001:db8::3/1067 Local: 2001:db8::3/23
> There is now 1 clients connected.
> Received from 2001:db8::3: 'binary 128'"
>
> But there's another problem with WSocket_WSAAsyncGetHostByName.
> AKAIK, this old API doesn't support IPv6. New API GetAddrInfo() handles
> both IPv4 and IPv6 but it is blocking. Should I try to emulate asynchron
> lookups using a thread? Ideas are welcome.
>
> --
> Arno Garrels
>
>
>
 Hi Arno,

As usual, I am against one thread per call approach for the sake of
scalability. I believe there must be another async way from Redmondians.

Regards,

SZ
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to