[cap-talk] OO interoperation via OCap, presentation level issues

[Baldur Johannsson]

I think the essential and minimal base of ocap communication is
asynchronus messages made up of two blocks:
 one block of capabilities and one block of bits/bytes. Where the
first cap in capabilities block is destination of the message.

Synchronus call/return, object serializations (for
passByConstruction/Copy) and indexing into caps-block semantics can
then be built on top of that.

And please note, Jed, that the word type has unfortunetly accrued too
many meanings.

Do you mean type as in designating those particular bits are to be
treated in that way?

Thoughts? Comments? Need for clarification?
Dont hesitate to ask.

-Baldur Jóhannsson
a small fan of KISS (keep it small and simple), something I
sense/suspect that ocaps
captures beautifully in computer security.