The DNS lookup changes are now all in SVN, with two samples updated to
test them.
I'll be adding wsoIcsDnsLookup to all my applications, but
wsoAsyncDnsLookup is more complicated since it means OnDnsLookupDone is
no longer called. A lot goes on in that event, state changing, error
handling for
One other long term DNS limitation with ICS is where multiple IP
addresses are returned, such as this one used regularly by every
Windows PC:
Looking up Address for: www.msftncsi.com, Family: AnyIPv4
IP Address is: 95.101.128.195
IP Address is: 95.101.128.169
or
Looking up Address for: pool.ntp
Only snag with TWSocketOptions is they are not easy to set for high
level protocol components, which may not make the underlaying sockets
available.
Well, HTTP and FTP clients (so I believe others too) do expose Socket
properties so it is easy to tune them; those components who hide Socket o
> I've did another patch (and another option wsoIcsDnsLookup) that
> allow using non-Winsock ICS DNS lookup though it's just not
> thoroughfully tested yet.
Thanks again, turned out to be rather easier than I expected since ICS
already uses a thread for IPv6 lookups, so the code has been reason
> Tunnelling is really a concept rather than a protocol. The HTTP
> client and server support the CONNECT command which is used for SSL
> proxies.
>
> There are no current ICS samples relating to SSL proxy or
> tunnelling.
Further to those comments yesterday, the main TWSocket component
al
Angus, thanks for testing my changes!
This patch indeed only calls DnsLookup before Connect transparently to client
software.
I've did another patch (and another option wsoIcsDnsLookup) that allow using
non-Winsock ICS DNS lookup though it's just not thoroughfully tested yet. In my
primitive t
