remoc
touche
remoc | touche | |
---|---|---|
6 | 4 | |
148 | 43 | |
3.4% | - | |
7.9 | 5.6 | |
about 1 month ago | 8 months ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | 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.
remoc
-
Inter-process Communication between two programs on Linux.
u/OP if you want to use unix/tcp socket directly check out https://crates.io/crates/remoc it works over both and is a WAY better idea then http...
-
the best way to pass parameters to egui
You can use an RPC framework to not invent the wheel from scratch like for example https://crates.io/crates/remoc Why? Because such program as an https proxy will likely often run as a daemon started via an init system for example systemd. As you can not start a GUI program as a daemon under unix the GUI wouldn't work anyway. It might even run on a headless server with any GUI and you might want to start you GUI remotely and connect to it.
-
What are some less popular but well-made crates you'd like others to know about?
remoc - a really good rpc framework with agnostic transport and encoding and support for observable/streamable objects.
-
Tsyncp: Channel-like primitives (mpsc, broadcast, etc) over TCP
We had the same challenge and developed Remoc for that. There also is Tarpc, however it does not support channels, only RPC.
-
Pubsub-like library for microservices?
Remoc might do what you want, basically channels generic for anything that implements AsyncRead and AsyncWrite. https://github.com/ENQT-GmbH/remoc/
touche
-
Web Framework for Rust Backend for a fun side-project
If you wish to keep it simple by staying away of async runtimes, I recommend my own thing that I built precisely for people that are learning Rust: https://github.com/reu/touche
- Options for thread-per-request or thread-per-connection web servers?
-
Rust API | Any good guides writing an API with the std lib?
Not really a guide, but I implemented this webserver library to teach Rust and HTTP concepts to my coworkers. It is (arguably) simple Rust code with minimal dependencies, so it may be useful for your studies: https://github.com/reu/touche
-
What are some less popular but well-made crates you'd like others to know about?
If you wish to checkout an alternative: https://github.com/reu/touche Ps: I am the author
What are some alternatives?
nvim-send - Essentially "nvim --remote-expr <expr>" / "nvim --remote-send <keys>" or "nvr --nostart --remote-send <keys>" in Rust
imara-diff - histo_diff
Coerce-rs - Actor runtime and distributed systems framework for Rust
versio - A version number manager
rmp-rpc - a msgpack-rpc rust library based on tokio
woodpecker - Drill is an HTTP load testing application written in Rust
postage-rs - The feature-rich, portable async channel library
polars - Dataframes powered by a multithreaded, vectorized query engine, written in Rust
lifeline-rs - A dependency injection library for message-based applications
Iron - An Extensible, Concurrent Web Framework for Rust
micromath - Embedded Rust arithmetic, 2D/3D vector, and statistics library
start-axum - Starter template for use with the Leptos web framework and Axum.