[Top][All Lists]

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

Re: feature-mtab-translator (v3)

From: Neal H. Walfield
Subject: Re: feature-mtab-translator (v3)
Date: Tue, 23 Jul 2013 11:46:55 +0200
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.8 Emacs/23.2 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)

At Mon, 22 Jul 2013 22:49:03 +0200,
Samuel Thibault wrote:
> Neal H. Walfield, le Mon 22 Jul 2013 21:50:02 +0200, a écrit :
> > At Fri, 19 Jul 2013 17:25:02 +0200,
> > Justus Winter wrote:
> > > * The translator used to traverse the translator tree and if it
> > >   encountered itself, it would deadlock. This is cleanly solved by
> > >   comparing the control ports of the current node and the mtab
> > >   translator.
> > 
> > I don't think you can reliably do this.  This assumes that the same
> > port is always used for accessing the the fsys facet, which is not
> > necessarily the case.
> What other port could it be?

Perhaps I don't completely understand the situation.

Here's what I'm thinking: if a program somehow fetches an fsys port,
there is no guarantee that the returned send right corresponds to a
unique port (even if this is currently the de facto case).  Consider
opening a file: the port identifies the peropen; every open results in
a new receive right.  Or, consider proxing.  If this is somehow
guaranteed not to be the case here, then I guess a numeric comparison
is acceptable.


reply via email to

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