Re: Throttling and blocking in cap/message-passing systems?
Tony Arcieri <[email protected]> Thu, 9 Jul 2015 01:21:09 -0700
| Newsgroups | gmane.comp.capabilities.general |
|---|---|
| Message-ID | <CAHOTMVKO3-UTWScmOQcY=k9b1hng9=9J8mEH8GQxftv+6PWd5w@mail.gmail.com> |
On Thu, Jul 9, 2015 at 12:14 AM, rmeijer <rmeijer-qWit8jRvyhVmR6Xm/[email protected]> wrote: > 1) Is anyone aware of papers that may be relevant to the design of such a > system, whether just message passing architecture related or specific to > capability based message passing architectures. Also papers showing that > this would be essentially a bad idea are very welcome at this point. Distributed Erlang systems sleep the sender "process" when the TCP send buffers are full and you attempt to send an "asynchronous" message, then resume it again when space in the buffer is available. This assumes you have some sort of concurrency context with a stack, whereas it sounds like you're stuck in CPS land. Other options are: 1) Raise an exception 2) Drop the message on the floor -- Tony Arcieri _______________________________________________ cap-talk mailing list [email protected] http://www.eros-os.org/mailman/listinfo/cap-talk