[cap-talk] OO interoperation via OCap [correction]

David-Sarah Hopwood david.hopwood at industrial-designers.co.uk
Sat May 17 18:15:32 CDT 2008


David-Sarah Hopwood wrote:
> Raoul Duke wrote:
>>> I think the essential and minimal base of ocap communication is
>>> asynchronous messages [...]
>>
>> Given that Caps are in the security field, should one worry about the
>> asynchronous default leading to buffer resource consumption?
> 
> The minimal base of object-cap communication is not asynchronous messaging;
> it's just messaging. Specifying asynchronous or synchronous is an
> overspecification if we are talking about capability systems in general.

To be more precise:

The minimal base of capability communication is not asynchronous messaging;
it's just messaging. Specifying asynchronous or synchronous is an
overspecification if we are talking about capability systems (whether or
not restricted to object-capability systems) in general.

-- 
David-Sarah Hopwood


More information about the cap-talk mailing list