Hi Maurizio, >> Since Wininet is not unicode enabled, I've changed all Char, PChar and >> String to Ansi except the variables used by ICS-function ParseUrl. >> I get about 60 Warnings :-( > > I see. I can try to adapt it to D2009. > It's working, but the warnings are all about ansistring-string conversion I could add an ansi version of function ParseUrl() This would probably remove the warnings.
>> Anyone used Winhttp instead Wininet for this ? >> It's unicode enabled and can handle WPAD which is commonly used now. > > Ok for unicode support, but why you are convinced that WPAD is not handled > by > WinINet? From http://msdn.microsoft.com/en-us/library/aa383993(VS.85).aspx I'm 100% sure: - All user reports I get are those who use WPAD. - We've opened a Microsoft support ticket for this issue and they confirmed that it won't work with WinInet. In Vista, there's an updated version on WinInet that can handle WPAD on IPv6 Paul -- 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
