4 ms·
Not always. Goblins[0] is an example of an actor system that supports both synchronous and asynchronous communication between actors, with synchronous communica
by ryukafalz 5y ago
Not always. Goblins[0] is an example of an actor system that supports both synchronous and asynchronous communication between actors, with synchronous communication only possible if both actors are in the same “vat” (a kind of event loop).
[0] https://docs.racket-lang.org/goblins/ https://docs.racket-lang.org/goblins/
- paroneayea 4y agoHi! Yeah I'm the author of Goblins :) Yes, Goblins' "vat" model descends from E, which supports the "hybrid worldview". http://www.erights.org/ http://www.erights.org/ I have a tendency to call Goblins objects "actors", though some people in the community like to point out that "distributed object" is preferable since synchronous call/return is not supported in actors. But yeah.