[systemd-devel] [RFC 0/6] A network proxy management daemon, systemd-proxy-discoveryd

[Daurnimator]

On 13 April 2015 at 07:12, Cameron Norman <camerontnorman at gmail.com> wrote:
> On Fri, Apr 10, 2015 at 5:17 AM, Tomasz Bursztyka
> <tomasz.bursztyka at linux.intel.com> wrote:
>> Hi,
>>
>> [snip]
>>
>> 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.
>>
>
> It seems that duktape is really not in a suitable shape to be packaged
> in distributions (https://github.com/svaarala/duktape/issues/94). Do
> you have any plans to get it into shape?
>
> Also, and I am just curious, what is the specific reasoning duktape is
> preferred? Smaller memory footprint?
>
> Thanks,
> --
> Cameron Norman


Have you looked into MuJS instead of duktape? http://mujs.com/
It has a C api similar to Lua, with all state encapsulated in an
opaque structure, that you interface with via a virtual stack.