[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Defualt socket server overriding

From: Neal H. Walfield
Subject: Re: Defualt socket server overriding
Date: Wed, 20 Jun 2007 20:07:43 +0200
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.4 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Wed, 20 Jun 2007 10:30:02 -0700,
Thomas Bushnell BSG wrote:
> On Wed, 2007-06-20 at 16:20 +0200, Neal H. Walfield wrote:
> > When we are just interested in
> > overriding a small parts of the environment and the rest represents a
> > reasonable default, this may be fine.  Such an approach is, however,
> > completely contrary to POLP.  I think the right direction is private
> > name spaces, which can be achieved by passing capabilities.  That was
> > the other part of my suggestion.
> Private namespaces are another excellent idea; they are perhaps harder
> to work into the current framework unless there's a trick I haven't
> thought of.

As I don't think you specifically addressed it, I'll repeat my main

One of the best private name spaces that we have, I think, is the
capability name space.  My proposal was to do the following:

  PFINETSERVER=fd:3 myprog 3</path/to/pfinet

Thus, the shell translates the symbolic name `/path/to/pfinet' in its
own naming context.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]