henet
Cap'n Proto
henet | Cap'n Proto | |
---|---|---|
10 | 67 | |
8 | 11,235 | |
- | 1.3% | |
0.0 | 9.2 | |
over 10 years ago | 8 days ago | |
Haskell | C++ | |
MIT 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.
henet
-
Microsoft wins FTC fight to buy Activision Blizzard
Halo was mostly all about single player and early multiplayer/local multiplayer but their online netcode has sucked since Blood Gulch. Lots of games do networking horribly, I have been in gamedev making networking and I hate most of what people do. The ones that have a clean natting, based on enet style reliable UDP channels, RakNet style punch are better (RakNet was good until Facebook bought it). It has come a long way but also fallen back. Valve source netcode (on github) is probably the best and you can check it out here. They started with the best in Quake networking, then to Source.
-
Multiplayer Networking Solutions
Enet already talked about in the thread
- What's an actually useful netcode package!
-
Porting SDL2 Game to the web, Emscripten tutorial
Probably not. It says Enet runs over UDP, which Web Browsers / WebAssembly / Emscripten don't provide. Web browsers / Emscripten provide TCP only (source). That, and Enet probably calls standard UNIX / Winsock functions, which Emscripten doesn't have. ENet would have to specifically support Emscripten as a target platform.
-
Game networking with QUIC
Are you familiar with enet ? It's a popular C library which implements optional reliability on top of UDP.
-
HTTP/3 becomes a standard, at last - Networking - Security
The other that is the base of most networking libs today is enet, one of the cleanest C networking libraries you will ever find. The RUDP and channels in it were very nice.
-
Making a multiplayer server
Inconsistencies can be prevented by ensuring the server handles all operations and does so in a given order, then transmits the results to clients. I wrote a little about this for my game Avoyd a long while ago. Clients (including a client running the server) send an edit request via reliable ordered UDP (e.g. using Enet, Raknet, Steam Networking etc.) and the server places these in a single queue then performs the edits and sends the results back also using reliable ordered UDP.
-
How I Taught the D Programming Language at a Russian University
I find this interesting. Vibe.d is async, but written in a sync fashion (in essence, the async is hidden in the i/o subsystem). For my class with grade-school students, I used enet (http://enet.bespin.org/) with a wrapper I wrote to automatically serialize messages.
-
what is the easiest way to add online multiplayer to a voxel game?
A popular simple low level open source reliable UDP library is ENet.
-
Speed Dreams needs you! (Call for devs)
-Improve the status of the Online Mode: This mode built with eNet, currently allows to create multiplayer races, but while it works acceptably well in a LAN, over the internet is unplayable presenting a huge lag, among other problems.
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.
What are some alternatives?
H - The full power of R in Haskell.
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
bindings-svm - Low level bindings to libsvm
Protobuf - Protocol Buffers - Google's data interchange format
bindings-levmar - Low level Haskell bindings to the C levmar (Levenberg-Marquardt) library
FlatBuffers - FlatBuffers: Memory Efficient Serialization Library
bindings-sc3 - Haskell bindings to the SuperCollider synthesis engine
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
bindings-DSL - Library and macros to simplify writing Haskell FFI code
Apache Thrift - Apache Thrift
bindings-libusb - Low level bindings to libusb
MessagePack - MessagePack serializer implementation for Java / msgpack.org[Java]