The paragraph that mentions them also links to rpc.capnp, which
describes these types and their use:
https://github.com/capnproto/capnproto/blob/master/c++/src/capnp/rpc.capnp
Quoting John (2018-11-17 03:29:13)
> https://capnproto.org/encoding.html glibly mentions SturdyRef and
> CapDescriptor
>
> Which, it would seem, are needed for one system to understand what is
> being sent to it by another system.
>
> But nowhere on the website is it explained what SturdyRef and
> CapDescriptor are, why they are, what the system trying interpret the
> message is intended to do with them, how they fit into the design.
>
> Does every message need them, or do we need one such table for each
> message type?
>
> What do we need them for, what do we do with them, what is in them? How
> do they fit into the design?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Cap'n Proto" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> Visit this group at https://groups.google.com/group/capnproto.
--
You received this message because you are subscribed to the Google Groups
"Cap'n Proto" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/capnproto.
