Re: [naviserver-devel] nsproxy API

[Stephen D. <sd...@gm...>]

On 10/6/06, Zoran Vasiljevic <zv...@ar...> wrote:
>
> etc ? Or ns_slave?
>
>     ns_slave eval arg
>     ns_slave config thepool option ?value option value ...?
>
> Hm... that's not bad. What do you think?
> I think ns_slave would be "opportune". The people will of course
> immediately ask: where is ns_master? But I guess you can't dance
> on all weddings...


That's not a bad idea. Tcl already has a concept of slave interps. The
difference being that ours run out-of-process.  There's a whole bunch
of other stuff that goes along with Tcl slave interps, but the core is
the same: you send a script to evaluate and a result comes back.


> Would you integrate that in the core code or would you leave this
> as a module? Actually, I keeep asking mylself why we still stick to
> modules when some fuctionality is obviously needed all the time
> (nslog or nscp for example)...


I think we need more modules, not less...  :-)