Re:Amazon Ion – A richly-typed, self-describing, hierarchica...
by NavinF on Saturday November 20, 2021 @12:25AM
(#29285806)
Capnp uses the name of your message, but not its full definition because that would make it impossible to extend protocols in a backwards compatible way. Without the ability to add new fields, making changes to your protocol would be impossible in large orgs.
I wonder if giving it a name based on the hash of the definition has been explored; like Unison [0] where all code is content addressable, but for just capnproto definitions. Is there a reason not to?
[0]: https://www.unisonweb.org