https://github.com/wolfulus/wolfrpc
My opinionated, not so "remote", RPC library.
https://github.com/wolfulus/wolfrpc
dotnet json netstandard netstandard20 netstandard21 rmi rpc transport unity
Last synced: about 1 month ago
JSON representation
My opinionated, not so "remote", RPC library.
- Host: GitHub
- URL: https://github.com/wolfulus/wolfrpc
- Owner: WoLfulus
- Created: 2022-08-23T18:18:50.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-12-02T01:30:33.000Z (over 1 year ago)
- Last Synced: 2025-11-16T06:18:18.294Z (5 months ago)
- Topics: dotnet, json, netstandard, netstandard20, netstandard21, rmi, rpc, transport, unity
- Language: C#
- Homepage: https://github.com/WoLfulus/WolfRpc
- Size: 47.9 KB
- Stars: 2
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# WolfRpc
Even though it has RPC in the name, this isn't that **remote** since transport is not something I'm worried about. If service calls can be dispatched from a serialized payload and results are serialized with caller identification, the transport is just a detail.
## Goals
- [ ] Everything must be async by default
- [ ] Requests (calls) must be serializable
- [ ] Responses (results) must be serializable
- [ ] Must support exceptions
- [ ] All requests and responses must be identifiable and give context to be matched as a pair
- [ ] Must play well with any kind of transport (socket, web, udp, message queues, ...)
- [ ] Must be able to use it in Unity (both server and consumer)
- [ ] Must be compatible with il2cpp
- [ ] Must be able to use it in net6+ (both server and consumer)