🚀 go-pugleaf

In article <MIB.91Mar18050418@geech.ai.mit.edu>, mib@geech.ai.mit.edu (Michael I Bushnell) writes:
|> In article <2991@redstar.cs.qmw.ac.uk> timk@cs.qmw.ac.uk (Tim Kindberg) writes:
|>    2 Sending port rights. Is there anyone out there sending port
|>    receive rights in messages?  I would very much like to hear about
|>    the application context in which you chose to do this, and how you
|>    found using this mechanism.
|> 
|> Port rights are sent constantly.  This is an essential part of the
|> Mach model.  In the GNU multi-server, port rights represent (among
|> other things) files, and filesystems hand port rights to clients when
|> they open a file or translate a pathname to a file (for a later stat,
|> for example).  The return port for an RPC is also sent as a port right
|> in the message header, and apart from some additional atomicity
|> guarantees, operates like a port right sent in a message.

The question here was about receive rights.  It sounds to me like
you've covered lots of reasons for passing around send rights.  I'd
also be interested in hearing of applications for passing of receive
rights.
--
Andy Lowry, lowry@ibm.com, (914) 784-7925
IBM Research, 30 Saw Mill River Road, P.O. Box 704, Yorktown Heights, NY 10598