News for hackers. Stuff that matters.
Re:Cap'n Proto 1.0 by mananaysiempre on Friday July 28, 2023 @05:38PM (#36913715)
There is also CapnP’s moral ancestor CapTP[1]/VatTP aka Pluribus developed to accompany Mark Miller’s E language (yes, it’s a pun, there is also a gadget called an “unum” in there), for the genealogy of which—including a reference to Barbara Liskov for promise pipelining and a number of other things in the CLU extension Argus—see his thesis[2].

(If I’m not misremembering, Mark Miller later wrote the OG promise proposal for JavaScript, except the planned extension for RPC never materialized and instead we got async/await, which doesn’t seem compatible with pipelining.)

The more recent attempts to make a distributed capability system in the image of E, like Spritely Goblins[3], also try for pipelining, so maybe if you hang out on cap-talk[4] you’ll hear a couple of other protocols that do it, if not ones with any real-world usage.

(And I again reiterate that, as neat as it is, promise pipelining seems to require programming with actual explicit promises, and at this point it’s well-established how gnarly that can get. One idea that I find interesting and little-known from the other side—event loops and cooperatively concurrent “active objects”—is “causality IDs” from DCOM/COM+ as a means of controlling object reentrancy, see CoGetCurrentLogicalThreadId in the Microsoft documentation and the discussion of CALLTYPE_TOPLEVEL_CALLPENDING in Effective COM[5].)

[1] http://erights.org/elib/distrib/captp/index.html

[2] http://erights.org/talks/thesis/index.html

[3] https://spritely.institute/goblins/

[4] https://groups.google.com/g/captalk/

[5] https://archive.org/details/effectivecom50wa00boxd/page/150

There are no comments on this comment yet.