[cap-talk] OO interoperation via OCap, presentation level issues
Raoul Duke
raould at gmail.com
Fri May 16 17:04:01 CDT 2008
> I think the essential and minimal base of ocap communication is
> asynchronus messages
Given that Caps are in the security field, should one worry about the
asynchronous default leading to buffer resource consumption? One can
build async on top of sync with more explicit buffering. (Dunno if
that matters; Erlang sure seems to do OK with async as the default,
although in a perf not necessarialy security way.)
sincerely.
More information about the cap-talk
mailing list