[e-lang] "Comm system"

[David Hopwood]

Kevin Reid wrote:
> (Posted to cap-talk as well as e-lang; please consider which lists to  
> reply to.)

(The suggestion below is applicable to both language and non-language-based
distributed systems.)

> Mark Miller said yesterday that he thought "comm system" was too
> generic, that there are too many things it could refer to.
> 
> (A comm system, in our existing terminology, is a program which  
> manages proxies for remote objects over some network/IPC protocol  
> (e.g. CapTP, boot-comm); serialization, resolution, pipelining,  
> whenBroken, etc.)
> 
> He suggested the term "remoting system". "remoting" is an unfamiliar  
> term to me, and I'd like to hear others' thoughts on these choices of  
> terminology.

Oz uses "distribution subsystem". I think that, or just "distribution system",
is a good choice for a system that implements distributed objects/messaging.
Note that this is the whole system, not the component of it that resides on a
single node.

-- 
David Hopwood <david.nospam.hopwood at blueyonder.co.uk>