[Pidgin] #4459: libpurple should use libproxy

[Pidgin]

#4459: libpurple should use libproxy
-----------------------------+----------------------------------------------
 Reporter:  kipple           |        Owner:           
     Type:  enhancement      |       Status:  new      
Milestone:  Patches welcome  |    Component:  libpurple
  Version:  2.3.1            |   Resolution:           
 Keywords:                   |  
-----------------------------+----------------------------------------------

Comment(by npmccallum):

 Some clarity might help here.

 libproxy uses the URL format for two reasons:
 1. PAC files require the URL form
 2. Some OSes provide multiple proxy configuration options for different
 protocols (http/https/socks/gopher/etc).

 In the first case you are at the mercy of the PAC file.  If your PAC file
 doesn't know how to return the proper proxy for non-http URLs, then there
 is a bug in your PAC file.  This is not a libproxy bug, it is by design.

 In the second case, if we do not find a protocol match we fall back on
 http and then socks.

 In short, using libproxy with "xmpp://talk.google.com" will provide the
 correct behavior in the second case and, so long as you have a properly
 written PAC file, the first case.

 I'd also like to point out that we (libproxy) are very easy to work with.
 We close bugs quickly and answer questions as best as we can.  If you find
 any problems or just have a few questions, don't hesitate to contact us.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/4459#comment:9>
Pidgin <http://pidgin.im>
Pidgin