Jason Rumney wrote:
Lennart Borgman <[EMAIL PROTECTED]> writes:
I did not believe it was such a mess.
It's not a mess. Although it is theoretically possible to write
complicated autoproxy scripts that use a different proxy for different
hosts, in practice all anyone ever uses is a single proxy and a list
of no-proxy hosts.
How does one find out this single proxy and the list of no-proxy hosts
then? Is not that complicated procedure with perhaps an ECMAscript to
call required?
While looking more at this I found that MS actually are providing an
API (WinHttpGetProxyForUrl) for this now on XP and W2k.
It is not an OS API, it is an Internet Explorer API, and the first
parameter is a handle to an open "INTERNET_SESSION", created by
another function in the same API, so if you start down that road
you'll end up having to continue, and that would restrict the
networking capabilities of Emacs to what is supported by IE. Not to
mention that IE is not Free, and thus unsuitable to build Free
software on top of.
I do not understand the difference between an OS and and IE API. Could
you explain? There is a page about WinHTTP that does not seem to make
such difference between WinINet and WinHTTP:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winhttp/http/about_winhttp.asp
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
