Add config module for querying PacRunner dæmon

[GoogleCodeExporter]

PacRunner runs as a service and gives proxy information over DBus. The PAC file 
is downloaded and the JS interpreter runs in only one process, rather than 
being duplicated in each client using libproxy.

This patch provides a libproxy module that queries PacRunner.

Original issue reported on code.google.com by dwmw2b@gmail.com on 8 Dec 2010 at 12:21

Attachments:

• 0001-Add-config-module-for-querying-PacRunner-d-mon.patch

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Well, PacRunner isn't tied to ConnMan. It can quite happily be used on its own, 
and can be configured by anything. ConnMan is just one thing that can poke 
PacRunner to tell it where to find the proxies. It would be simple to make 
NetworkManager (or anything else) give it that information too.

And it's not really for MeeGo either; MeeGo itself is probably going to drop 
the 'real' libproxy completely and just use the tiny libproxy replacement that 
PacRunner provides, since it only *ever* wants the "just ask PacRunner" mode.

Original comment by dwmw2b@gmail.com on 4 Jan 2011 at 5:31

[GoogleCodeExporter]

That's kind of a shame, last time I check I did not see any static proxy 
configuration in PacRunner, and PacRunner does not do much more then running 
PAC, which is already handled by libproxy. Why not wrapping libproxy into D-Bus 
as suggested in issue 120. If you needed a V8 runner that would have been easy 
to do, and if you only need one setup just install the libproxy plugins you 
need.

Original comment by nicolas.dufresne@gmail.com on 6 Jan 2011 at 8:13

[GoogleCodeExporter]

Patch still hasn't been applied. Ping?

Original comment by dwmw2b@gmail.com on 29 Apr 2011 at 8:38

[GoogleCodeExporter]

Updated patch.

Original comment by dwmw2b@gmail.com on 7 Jun 2013 at 1:47

Attachments:

• 0001-Add-config-module-for-querying-PacRunner-d-mon.patch