https://bugzilla.novell.com/show_bug.cgi?id=397249 Summary: include libproxy in the distribution Product: openSUSE 11.1 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dominique.leuenberger@tmf-group.com QAContact: qa@suse.de Found By: --- *** DISCLAIMER *** Description shamelessly copied from the website of the library: http://code.google.com/p/libproxy/ *** END DISCLAIMER *** *** Status *** - Working packages for newer versions of openSUSE can be found in OBS home:dimstar - LibSoup can be compiled already against libproxy *** END Status *** *** Shameless plug *** The Problem Problem statement: Applications suck at correctly and consistently supporting proxy configuration. Proxy configuration is problematic for a number of reasons: 1. There are a variety of places to get configuration information 2. There are a variety of proxy types 3. Proxy auto-configuration (PAC) requires Javascript (which most applications don't have) 4. Automatically determining PAC location requires an implementation of the WPAD protocol These issues make programming with support for proxies hard. Application developers only want to answer the question: Given a network resource, how do I reach it? Because this is their concern, most applications just give up and try to read the proxy from an environment variable. This is problematic because: 1. Given the increased use of mobile computing, network switching frequently occurs during the lifetime of an application 2. Each application is required to implement the (non-trivial) WPAD and PAC protocols, including a Javascript engine 3. It prevents a network administrator from locking down settings on a particular host or user 4. In most cases, the environmental variable is almost never correct by default The Solution libproxy exists to answer the question: Given a network resource, how do I reach it? It handles all the details, enabling you to get back to programming. GNOME? KDE? Command line? WPAD? PAC? Network changed? It doesn't matter! Just ask libproxy what proxy to use: you get simple code and your users get correct, consistant behavior and broad infrastructure compatibility. Why use libproxy? libproxy offers the following features: * extremely small core footprint (< 35K) * no external dependencies within libproxy core (libproxy plugins may have dependencies) * only 3 functions in the stable external API * dynamic adjustment to changing network topology * a standard way of dealing with proxy settings across all scenarios * a sublime sense of joy and accomplishment -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.