[e-lang] E and FUSE-j integration
Toby Murray
toby.murray at comlab.ox.ac.uk
Wed Sep 26 12:52:54 EDT 2007
On Wed, 2007-09-26 at 07:54 -0700, Mark Miller wrote:
> On 9/26/07, Kevin Reid <kpreid at mac.com> wrote:
> > When the callee is invoked, it sends an appropriate message into the
> > vat, and then blocks waiting for notification that the result promise
> > has resolved.
> >
> > There don't seem to be pretty operations for doing this; Vat#now/1
> > only does one-turn operations. MarkM, is there an existing mechanism
> > for this? If not, it shouldn't be hard to implement -- we just need a
> > when-resolved-reactor which can wake up a thread, which we attach to
> > the result promise.
>
> You are correct both that there isn't currently such a mechanism, and
> that it should be fairly straightforward. The result would support the
> Erlang style of concurrency, where a caller in effect build a
> synchronous RPC out of asynchronous msgs. This would, of course,
> re-introduce all the normal deadlock dangers, but it could be done.
I take it that the introduction of deadlock dangers cannot be avoided if
one is going to implement a synchronous interface, not matter how it's
done. Is that right?
More information about the e-lang
mailing list