Cap'n Proto
rpclib
Our great sponsors
Cap'n Proto | rpclib | |
---|---|---|
66 | 4 | |
11,180 | 1,598 | |
1.6% | 0.0% | |
9.2 | 0.0 | |
1 day ago | over 1 year ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Cap'n Proto
-
Mysterious Moving Pointers
Yeah I pretty much only use my own alternate container implementations (from KJ[0]), which avoid these footguns, but the result is everyone complains our project is written in Kenton-Language rather than C++ and there's no Stack Overflow for it and we can't hire engineers who know how to write it... oops.
[0] https://github.com/capnproto/capnproto/blob/v2/kjdoc/tour.md
-
Show HN: Comprehensive inter-process communication (IPC) toolkit in modern C++
- may massively reduce the latency involved.
Those sharing Cap'n Proto-encoded data may have particular interest. Cap'n Proto (https://capnproto.org) is fantastic at its core task - in-place serialization with zero-copy - and we wanted to make the IPC (inter-process communication) involving capnp-serialized messages be zero-copy, end-to-end.
That said, we paid equal attention to other varieties of payload; it's not limited to capnp-encoded messages. For example there is painless (<-- I hope!) zero-copy transmission of arbitrary combinations of STL-compliant native C++ data structures.
To help determine whether Flow-IPC is relevant to you we wrote an intro blog post. It works through an example, summarizes the available features, and has some performance results. https://www.linode.com/blog/open-source/flow-ipc-introductio...
Of course there's nothing wrong with going straight to the GitHub link and getting into the README and docs.
Currently Flow-IPC is for Linux. (macOS/ARM64 and Windows support could follow soon, depending on demand/contributions.)
-
Condvars and atomics do not mix
FWIW, my C++ toolkit library, KJ, does the same thing.[0]
But presumably you could still write a condition predicate which looks at things which aren't actually part of the mutex-wrapped structure? Or does is the Rust type system able to enforce that the callback can only consider the mutex-wrapped value and values that are constant over the lifetime of the wait? (You need the latter e.g. if you are waiting for the mutex-wrapped value to compare equal to some local variable...)
[0] https://github.com/capnproto/capnproto/blob/e6ad6f919aeb381b...
- Cap'n'Proto: infinitely faster than Protobuf
-
I don’t understand zero copy
The second one is to encode data in such a way that you can read it and operate on it directly from the buffer. You write data in a layout that is the same, or easily transformed as types in memory. To do that you usually need to encode with a known schema, only Sized types to efficiently compute fields locations as offsets in the buffer, and you usually represent pointers as offset into the encode. You can look at capnproto protocol for instance https://capnproto.org/
-
OpenTF Renames Itself to OpenTofu
Worked well for Cap'n Proto (the cerealization protocol)! https://capnproto.org/
-
A Critique of the Cap'n Proto Schema Language
With all due respect, you read completely wrong.
* The very first use case for which Cap'n Proto was designed was to be the protocol that Sandstorm.io used to talk between sandbox and supervisor -- an explicitly adversarial security scenario.
* The documentation explicitly calls out how implementations should manage resource exhaustion problems like deep recursion depth (stack overflow risk).
* The implementation has been fuzz-tested multiple ways, including as part of Google's oss-fuzz.
* When there are security bugs, I issue advisories like this:
https://github.com/capnproto/capnproto/tree/v2/security-advi...
* The primary aim of the entire project is to be a Capability-Based Security RPC protocol.
- Cap'n Proto: serialization/RPC system – core tools and C++ library
-
Sandstorm: Open-source platform for self-hosting web app
I like how they use capability-based security [0] and use Cap'n Proto protocol. This is another technology that is slow to get broad adoption, but has many things going for when compared to e.g. Protocol Buffers (Cap'n Proto is created by the primary author of Protobuf v2, Kenton Varda).
[0] https://sandstorm.io/how-it-works#capabilities
[1] https://capnproto.org
-
Flatty - flat message buffers with direct mapping to Rust types without packing/unpacking
Related but not Rust-specific: FlatBuffers, Cap'n Proto.
rpclib
-
Is there a way to keep the client alive in rpclib?
If by rpclib you mean this: https://github.com/rpclib/rpclib then it's not clear what you're talking about. The code for that client retains the connection to the server for the duration of the connection, though of course if you simply wait for too long without sending anything the connection will time out and get torn down.
-
rpclib is looking for a new maintainer
Thanks for all your hard work in the past years. I'm not able to take over as a maintainer, but you mentioned CI rot and I can take thorough look at that! I opened a small PR refactoring the AppVeyor configuration.
What are some alternatives?
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
Protobuf - Protocol Buffers - Google's data interchange format
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
FlatBuffers - FlatBuffers: Memory Efficient Serialization Library
nanomsg - nanomsg library
Apache Thrift - Apache Thrift
eCAL - Please visit the new repository: https://github.com/eclipse-ecal/ecal
MessagePack - MessagePack serializer implementation for Java / msgpack.org[Java]
simple-rpc-cpp - a simple RPC wrapper generator to C/C++ functions