The following two patches attempt to add support to libzypp for dynamic detection of HTTP proxies. On a mobile device, a simple static configuration of proxies per scheme (http/ftp/etc.) is not sufficient. Complex corporate environments may provide a proxy autoconfig script which returns *different* proxies for different URLs (especially internal vs. external), and there may be no single proxy which can satisfy all requests. And the whole thing changes when you take the machine *outside* the corporate environment, and you want the system to cope with that change without manual reconfiguration. The solution to this problem is libproxy — a library which applications can use to ask the simple question "which proxy do I use for this URL?". Multiple implementations of the trivial libproxy API are possible; in future versions of MeeGo we won't actually use the original, which has various implementation issues — instead we'll provide a simple library called 'libproxy.so.0' which just makes D-Bus calls to a 'PacRunner' dæmon that receives proxy information from ConnMan based on the current network connections, and serves clients based on that information. -- David Woodhouse Open Source Technology Centre David.Woodhouse@intel.com Intel Corporation -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org