Francois PIETTE wrote:
>> 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.
>
> Having
Francois PIETTE wrote:
I'm going to look at how to implement IPv6 in ICS and wonder
if support for winsock below v2.2 was actually required in
ICS v7?
>>>
>>> No, I don't believe ICS v6 and v7 need to support any OSs earlier
>>> than Windows 2000, since they are long out of support
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.
Having async operation is really mandatory.
I'm going to look at how to implement IPv6 in ICS and wonder
if support for winsock below v2.2 was actually required in
ICS v7?
No, I don't believe ICS v6 and v7 need to support any OSs earlier than
Windows 2000, since they are long out of support and there is no need
for them to support new app
I'm going to look at how to implement IPv6 in ICS and wonder
if support for winsock below v2.2 was actually required in
ICS v7?
No, I don't believe ICS v6 and v7 need to support any OSs earlier than
Windows 2000, since they are long out of support and there is no need for
them to support new a
if support for winsock below v2.2 was actually required in
ICS v7?
As Wiki says,
Version 2.1 of Winsock was supplied in an add-on package for Windows 95.
It was an integral component of Windows 98, Windows NT 4.0, and all
subsequent Windows releases. (Microsoft did not supply implementations o
Anton Sviridov wrote:
> There's a socket lib written on C++ which seems to have async v6
> resolving:
>
[..]
> gethostby* functions has been replaced by getnameinfo/getaddrinfo."
Yes, that is the recommended replacement.
>
> I looked at the code, but they did something strange there, I can'
There's a socket lib written on C++ which seems to have async v6 resolving:
"2.1.1: Tcp socket Reconnect now works again. Improved ipv6 support.
Asynchronous resolver now works with ipv6 too. Safer pointer handling using STL
auto_ptr in some cases. Thread safety improvements, gethostby* function
Angus Robertson - Magenta Systems Ltd wrote:
>> 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.
>
> Yes definitely, we must be consistent with everything else, no
> blocking allowed in ICS!
O
Fastream Technologies wrote:
>>
>> 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.
>>
> 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.
Yes definitely, we must be consistent with everything else, no blocking
allowed in ICS!
How do we test IPv6 host lookups, presumably need an
On Thu, May 20, 2010 at 7:42 PM, Arno Garrels 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
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
> 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 w
Angus Robertson - Magenta Systems Ltd wrote:
>> I'm going to look at how to implement IPv6 in ICS and wonder
>> if support for winsock below v2.2 was actually required in
>> ICS v7?
>
> No, I don't believe ICS v6 and v7 need to support any OSs earlier than
> Windows 2000, since they are long out o
> I'm going to look at how to implement IPv6 in ICS and wonder
> if support for winsock below v2.2 was actually required in
> ICS v7?
No, I don't believe ICS v6 and v7 need to support any OSs earlier than
Windows 2000, since they are long out of support and there is no need for
them to support ne
> if support for winsock below v2.2 was actually required in
> ICS v7?
As Wiki says,
Version 2.1 of Winsock was supplied in an add-on package for Windows 95. It was
an integral component of Windows 98, Windows NT 4.0, and all subsequent Windows
releases. (Microsoft did not supply implementation
Hi all,
I'm going to look at how to implement IPv6 in ICS and wonder
if support for winsock below v2.2 was actually required in
ICS v7?
--
Arno garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit
18 matches
Mail list logo
