nng-haskell
nng
| nng-haskell | nng | |
|---|---|---|
| 2 | 9 | |
| 3 | 3,567 | |
| - | 0.9% | |
| 10.0 | 9.0 | |
| over 1 year ago | 6 days ago | |
| Haskell | C | |
| MIT License | MIT License |
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.
nng-haskell
nng
- nng is "nanomsg next generation", a wire-compatible C99 rewrite of the C library libnanomsg, with a similarly permissive MIT license. Pub/Sub, RPC-style Request/Reply, or Service Discovery, without worrying about details like connection management or retries.
-
RPC lib?
I just published the other day some bindings to the NNG message passing library (https://nng.nanomsg.org/). You can do request/reply, publish/subcribe and other communication patterns. It's trivial to serialize (with Binary for example) any data structure and pass it around the network:
-
[ANN] nng: Bindings for NNG (https://github.com/nanomsg/nng)
I put together quickly a binding to the NNG! library, it's simply a fork of the existing binding to Nanomsg! updated to work with NNG using the "compatible API". For basic usage seems to work pretty well:
-
Neovim architecture
I’m considering using msgpack + nng or msgpack + zmq
-
Any good lightweight c++ local socket library for embedded Linux?
I've found NNG to be high quality, also has less restrictive license. https://nng.nanomsg.org/
-
What is the best (and easy) way to make 2 different python projects communicate? They are on the same server for now but have different conda envs.
for communication between a Discord bot and other applications on the same machine I have used ZeroMQ - relatively easy to use, very portable but still flexible enough. (I've heard though that ZeroMQ has been somewhat superseded by nng nowadays)
-
I hate ASIO and I can't be alone.
I agree with this, but would add NNg as a good messaging library. It’s the successor to the spiritual successor of ZeroMQ.
- NNG – nanomsg-NG (rewrite of nanomsg)
-
How to use socket programming in cpp to chat over the same Wi-Fi network
you can also look into https://github.com/nanomsg/nng
What are some alternatives?
typed-protocols - Session types framework with support of protocol pipelining.
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
zmqpp - 0mq 'highlevel' C++ bindings
uvw - Header-only, event based, tiny and easy to use libuv wrapper in modern C++ - now available as also shared/static library!
cpp-httplib - A C++ header-only HTTP/HTTPS server and client library
cppzmq - Header-only C++ binding for libzmq
coz - Coz: Causal Profiling
distributed-process-tests - Cloud Haskell core library
libmpack - Simple implementation of msgpack in C
libcurl-cxx-std-networking-integration - Demonstration of libcurl integration into C++ 23 standard networking
nsq - A realtime distributed messaging platform
nanomsg-haskell - Haskell bindings to nanomsg