Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @project1enigma@chaos.social
always tired@project1enigma@chaos.social (2026-09-25 20:58:05)
@dthompson
OCapN/CapTP might just be adding async and native cryptography to Corba (again in spirit, not in the sense of actual technical heritage or *conscious* reinventing).
---Reply---
dave@dthompson@toot.cat (2026-09-25 21:47:15)
@project1enigma corba strikes me as the javafication of an actor-like system. it's similar in the sense that it's an RPC protocol with object references. it's different in that those object references are not capabilities, it has schemas (using IDL), and doesn't facilitate peer-to-peer connectivity. it looks a hell of a lot more complicated than ocapn is, too.
Reply
---Replies---
dave@dthompson@toot.cat (2026-09-25 22:08:46)
@project1enigma oh and I guess, as you already pointed out, there doesn't seem to be a notion of eventual results (promises) so it's also not async friendly.