[gold-devel] What do we want to provide?

[Nathan Ladd]

I've been thinking over RPC, and I've pretty much come into agreement with
Justin on everything he had in mind, but I'll spill that out here just so we
have it in a permanent home (and we can discuss it further):

1) RPC communication is done through simple Connections and proxy objects.
Connections are like uni-directional sockets. You don't have to respond to a
Connection request with a Connection request to the source; you might just
want one way traffic.

2) When an object's parent is destroyed, the RPC system reparents it in some
sort of graveyard, and adjusts everyone's proxy objects accordingly.

3) Basically, the only methods we need are for the creation of Connections,
and somehow creating proxy objects for those Connections. In fact,
Connection handling methods can likely exist inside proxy objects.

On 10/19/05, Justin Hibbits <jrh29 at alumni.cwru.edu> wrote:
>
> Alright, to make good use of the mailing lists:
>
> What exactly do we want to provide to a) the user, and b) the developer?
>
> Adam posted the list of classes we came up with in March, but I don't
> think
> it's complete enough, and the behavior isn't fleshed out. So I ask you
> guys.
>
> I don't want a list of classes, I want a set of behaviors that we as an OS
> provider -- kernel, user libraries, and user interface -- should provide.
>
> I await your thoughts,
>
> - Justin
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/gold-devel/attachments/20051027/30d79ab0/attachment.htm>