Like gRPC except significantly worse
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
NGnius (Graham) 6619db9128 Update versions 6 months ago
.github Update project info 8 months ago
nrpc Misc improvements/fixes for USDPL 7 months ago
nrpc-build Misc improvements/fixes for USDPL 7 months ago
nrpc-codegen-test Misc improvements/fixes for USDPL 7 months ago
.gitignore Create MVP of nRPC codegen 11 months ago
Cargo.lock Update versions 6 months ago
Cargo.toml Create MVP of nRPC codegen 11 months ago
LICENSE Create LICENSE 11 months ago
README.md Update project info 8 months ago

README.md

nRPC nRPC-build

nRPC

NG's custom spin of gRPC. Intended to be decoupled from the network layer for use with websockets.

About

nRPC provides the glue logic from protobuf declarations to client and server Rust code. The server-side logic and client-server networking is not implemented. This makes it almost, but not quite, a gRPC implementation in Rust. To really drive that idea home, nRPC stands for nRPC Remote Procedure Call -- almost like what gRPC stands for.

Since the network layer is not provided, this will never be fully compliant with gRPC specifications. On the other hand, gRPC can't be used in browsers but nRPC could be used to write something that does. Since nRPC is just a hobby project, think of it like a cheap knock-off -- compliance with gRPC is best-effort where possible.

Why?

I wanted a well-known RPC library that could work with a client in a browser. The most popular RPC library seemed to be gRPC, except that didn't support browsers. So I made something that fit my requirements.