[systemd-devel] [RFC 0/6] A network proxy management daemon, systemd-proxy-discoveryd
Lucas De Marchi
lucas.de.marchi at gmail.com
Thu Aug 13 14:03:10 PDT 2015
Hi Tomasz,
On Fri, Apr 10, 2015 at 9:17 AM, Tomasz Bursztyka
<tomasz.bursztyka at linux.intel.com> wrote:
> Hi,
>
> As it has been discussed in the systemd hackfest during the Linux Conference
> Europe, one daemon could centralize the management of all network proxy
> configurations. Idea is something user can do per-application (like in
> firefox for instance) or broader (per-DM like in Gnome), user could do it
> once and for all through such daemon and applications would then request it
> to know whether or not a proxy has to be used and which one.
>
> As a notice, this is nothing new. Such standalone daemon has been already
> done by the past, pacrunner. systemd-proxy-discoveryd will more or less
> implement the same ideas with improvements. It will get rid of big JS
> engines like spidermonkey or v8 which are overkill for the tiny PAC files
> to be executed on, for instance. From pacrunner experience, APIs will be
> also improved.
>
> This one is using - at least in this RFC - the duktape JS engine to run
> the PAC files. Note it is not provided in this patchset. Latest version
> 1.2.x was used.
>
> Next features to come are a bit detailed in the TODO (last patch).
>
> Tomasz Bursztyka (6):
> proxy-discoveryd: Basic core added
> proxy-discoveryd: Add the basics for parsing the default configuration
> proxy-discoveryd: Add PAC support through duktape js engine
> proxy-discoveryd: Execute the PAC based proxy in a thread
> proxy-discoveryd: Add the basic parts for handling DBus methods
> update TODO
What happened to this patch set? Are you going to send a new version?
Lucas De Marchi
More information about the systemd-devel
mailing list