Hi, Cap'n Proto hasn't implemented level 3 yet, but I don't think the requirement you quote is actually looking for it. "Level 3" refers to automated three-party handoff, a feature that almost no other protocol out there has in the first place. I suspect 3PH will be very useful it IoT scenarios, but it's probably not what the requirement is asking for.
Cap'n Proto's C++ library does indeed have a few mechanisms for detecting disconnects. Calls that are in-flight when a disconnect occurs will throw an exception of the "DISCONNECTED" type. Additionally, you can register a callback to be called on disconnect. It is up to the application to decide what to do once a disconnection is detected, though "reconnect and try again" is often a fine answer. -Kenton On Thu, May 4, 2017 at 5:18 PM, Hedge Hog <[email protected]> wrote: > > Hi, > I have another question in evaluating Cap'n Proto against the following > middle requirement: > > > > *Idempotent Connect and ReconnectComponents shall be able to connect and > reconnect to a running system without requiring a full restart of the > real-time stack. This requirement supposes that the transport stack > provides measures to detect disconnects and connects to nodes to allow > state synchronization of components if necessary.* > From reading [1], sections 'Handling disconnects' and 'RPC Protocol', my > understanding is that level-3 of the CP protocol would go some way to > meeting this requirement. The 3rd-party client side code (in this case > Machinekit) would be responsible for synchronization - correct? > > What level of this RPC protocol is implemented in Cap'n Proto v0.6? > > [1]: https://capnproto.org/rpc.html > > Appreciate any other insight you can share. > > Best wishes > Hedge > > -- > 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.
