[meego-packaging] A new libproxy 0.4.5
Li, Yan I
yan.i.li at intel.com
Wed Aug 25 00:55:23 PDT 2010
On Wed, Aug 25, 2010 at 03:28:21PM +0800, Woodhouse, David wrote:
> On Wed, 2010-08-25 at 04:37 +0100, Li, Yan I wrote:
> > Dear List,
> > I'm to upgrade libproxy to latest upstream release 0.4.5. Please help
> > to test it if you believe your program maybe affected by this.
> > http://build.meego.com/package/show?package=libproxy&project=home:yanli:branches:Trunk:Testing
> > The major visible change is now the WebKit pacrunner is no longer a
> > module but built-in. Which is good I think since supporting PAC is
> > essential for a fully functional proxy library.
> Hm. But that means we're loading the PAC file and running the JS
> interpreter again in every client application.
The PAC script must be run on every distinct HTTP request, this is by
design of PAC. The libproxy may cache and reuse the result for
identical PAC input sent within a short time but I think that's only a
nice to have. IE is running PAC for one hostname only once in 30
minutes, but that also brings up some problems (such as querying
network environment in PAC upon which decisions are made).
> I think it would be much better for the libproxy users *only* to pass
> the desired URL off to a separate dæmon via DBus, and get given the
Sure. But this is a feature request, and it shouldn't block upgrading
libproxy to latest upstream version.
> We also need to fix proxy autodetection -- recent versions of ConnMan
> provide PAC information obtained automatically from DHCP / VPN / etc.
> and we should be using it.
MeeGo Team, Opensource Technology Center, SSG, Intel
Office tel.: +86-10-82171695 (inet: 8-758-1695)
OpenPGP key: 5C6C31EF
IRC: yanli on network irc.freenode.net
More information about the MeeGo-packaging