Hi Ralph, For basically the entire history of Cap'n Proto RPC, I've been claiming that level 3 would be implemented "soon", but so far it hasn't actually happened. Today, I can once again suspect that level 3 will be implemented "soon" for use cases inside Cloudflare (where I currently work)...
As for level 4, to be honest I have so far never actually run into a use case in real projects where I thought it was needed. I certainly can come up with hypothetical use cases, but I guess they don't appear in practice much in the kind of work I do? Unfortunately I don't have time to work on Cap'n Proto features that I don't immediately need, so if I don't run into a use case myself then we may have to rely on a volunteer stepping up. -Kenton On Mon, Nov 19, 2018 at 9:31 AM <[email protected]> wrote: > Just that question... > > for knowing why take a quick look here > https://gitlab.com/causal-rt/causal/blob/master/include/causal/core.hpp#L211-222 > Why? > * might be interessting > * file is quite slim and describes mostly just how everything is connected. > * the highlighted code is a concept I call junction in this context. > * junctions are dedicated to ensure aspects(lockable, thread-safe data) > being lockable and sync across networks. > * Cap'n Proto level 4 would be the perfect fit for that task. Still will > do for now using what there is. > > Nice work, thanks > BR Ralph > > -- > 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.
