cereal
Protobuf
cereal | Protobuf | |
---|---|---|
13 | 174 | |
3,996 | 63,731 | |
0.7% | 0.6% | |
1.3 | 10.0 | |
2 months ago | about 16 hours ago | |
C++ | C++ | |
BSD 3-clause "New" or "Revised" License | 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.
cereal
- Ser20, a C++20 fork of cereal
-
Added reflection to C++ just to make my game work.
I'd stick with cereal for serialization
- Cereal Pack - a C++ schema serialization library
- Is there any good binary serializer & deserializer for C / C++?
-
Pataro II: Pataro Harder
Today I'm back to working on Pataro, the roguelike built on libtcod that made up much of my Hacktoberfest efforts. I had been assigned to an issue requesting the addition of serialization and deserialization, but unfortunately ran out of time and wasn't able to finish the former or start the latter. I ran into issues with Cereal, and had a hard time figuring out the structure of the program and how to go about implementing serialization for all the relevant components. At the end of that attempt I mentioned that if I were to try again I'd start by testing out Cereal separately and getting a handle on that before trying to implement it in Pataro - so that's what I'm doing today.
-
Hacktoberfest 5
I am once again working on Pataro today, and I've succeeded in clearing up some issues and creating new ones. I've been stuck on an issue where Visual Studio was raising errors in the portion of the code where I call the cereal archive on some types, but was able to clear up that issue by moving the save function definitions out of their respective headers and into the corresponding .cpp files. Examining this repo and its use of cereal again, I was able to get a bit clearer of an idea of how it's implemented, and I included just about every relevant cereal header I could find to try and avoid any issues like the previous one popping up again (with the intention of later removing whichever I can to avoid redundant inclusions).
-
Hacktoberfest 4
On the Pataro front, I've started looking at other examples of people using cereal for their games. It seems to be a popular choice for roguelike games like this, so hopefully I can figure out both the syntax problems I'm facing, as well as logical ones like how the program should be structured to have all the necessary data properly serialized and deserialized.
-
Hacktoberfest 3
Progress on one front but roadblocks on another. After my post yesterday outlining my plans to add serialization to Pataro I ran into some issues with calling the archive class in cereal wherein the call wouldn't go through due to an incorrect number of arguments. This happened with both vector and size_t data members, and I'm still investigating why.
-
Binary serialization library for at least C++17?
This is the simplest serialization library I saw. You only need to add one method to your class and you can stream it to desired archive. It supports binary as well as json, XML and others. https://github.com/USCiLab/cereal
- Google Protobuf vs JSON vs [insert candidate here]
Protobuf
-
Hitting every branch on the way down
It's because they changed the versioning format: https://github.com/protocolbuffers/protobuf/releases?page=5
But I suppose old version still receive bugfixes.
-
Reverse Engineering Protobuf Definitions from Compiled Binaries
For at least 4 years protobuf has had decent support for self-describing messages (very similar to avro) as well as reflection
https://github.com/protocolbuffers/protobuf/blob/main/src/go...
Xgooglers trying to make do on the cheap will just create a Union of all their messages and include the message def in a self-describing message pattern. Super-sensitive network I/O can elide the message def (empty buffer) and any for RecordIO clone well file compression takes care of the definition.
Definitely useful to be able to dig out old defs but protobuf maintainers have surprisingly added useful features so you don’t have to.
Bonus points tho for extracting the protobuf defs that e.g. Apple bakes into their binaries.
- Show HN: AuthWin – Authenticator App for Windows
-
Create Production-Ready SDKs With gRPC Gateway
gRPC Gateway is a protoc plugin that reads gRPC service definitions and generates a reverse proxy server that translates a RESTful JSON API into gRPC.
-
Create Production-Ready SDKs with Goa
To use more recent versions of protoc in future applications, you can download them from the Protobuf repository.
-
Roll your own auth with Rust and Protobuf
Use the Protobuf CLI protoc and the plugin protoc-gen-tonic.
-
Add extra stuff to a “standard” encoding? Sure, why not
> didn’t find any standard for separating protobuf messages
The fact that protobufs are not self-delimiting is an endless source of frustration, but I know of 2 standards:
- SerializeDelimited* is part of the protobuf library: https://github.com/protocolbuffers/protobuf/blob/main/src/go...
- Riegeli is "a file format for storing a sequence of string records, typically serialized protocol buffers. It supports dense compression, fast decoding, seeking, detection and optional skipping of data corruption, filtering of proto message fields for even faster decoding, and parallel encoding": https://github.com/google/riegeli
-
Block YouTube Ads on AppleTV by Decrypting and Stripping Ads from Profobuf
It looks like it is in fact universal. Just glancing at the code here, it looks like the tool searches any arbitrary file for bytes that look like encoded protobuf descriptors, specifically looking for bytes that are plausibly the beginning of a FileDescriptorProto message defined here:
https://github.com/protocolbuffers/protobuf/blob/main/src/go...
This takes advantage of the fact that such descriptors are commonly compiled into programs that use protobuf. The descriptors are usually embedded as constant byte arrays. That said, not all protobuf implementations embed the descriptors and those that do often have an option to inhibit such embedding (at the expense of losing some dynamic introspection features).
- How to learn to use protoc in 21 easily infuriating steps
-
What's involved in protobuf encoding?
Not much. You can check the source code in https://github.com/protocolbuffers/protobuf. For example, for serializing a boolean in C#: https://github.com/protocolbuffers/protobuf/blob/main/csharp/src/Google.Protobuf/WritingPrimitives.cs#L165. Strings and objects are a bit more complicated, but it is all about turning the data into its byte representation.
What are some alternatives?
Boost.Serialization - Boost.org serialization module
FlatBuffers - FlatBuffers: Memory Efficient Serialization Library
SBE - Simple Binary Encoding (SBE) - High Performance Message Codec
MessagePack - MessagePack implementation for C and C++ / msgpack.org[C/C++]
Magic Enum C++ - Static reflection for enums (to string, from string, iteration) for modern C++, work with any enum type without any macro or boilerplate code
Apache Parquet - Apache Parquet
Bitsery - Your binary serialization library
Bond - Bond is a cross-platform framework for working with schematized data. It supports cross-language de/serialization and powerful generic mechanisms for efficiently manipulating data. Bond is broadly used at Microsoft in high scale services.
json - JSON for Modern C++
Protobuf.NET - Protocol Buffers library for idiomatic .NET