tonic-server-dispatch
| Crates.io | tonic-server-dispatch |
| lib.rs | tonic-server-dispatch |
| version | 0.5.0 |
| created_at | 2025-03-15 05:02:21.150382+00 |
| updated_at | 2025-04-30 01:18:32.151993+00 |
| description | A request-dispatch level for tonic-Server. |
| homepage | |
| repository | https://github.com/WuBingzheng/tonic-server-dispatch |
| max_upload_size | |
| id | 1593283 |
| size | 28,758 |
(WuBingzheng)
documentation
https://docs.rs/tonic-server-dispatch
README
A typical architecture of network service is that after receiving a request, the network tasks dispatch it to the business tasks according to some fields. In this way, requests for the same content can be dispatched in the same task to avoid shared state or locking. This tokio tutorial gives detailed description.
The same is true in tonic's gRPC server. The dispatch of requests
from network tasks to the business task has a pattern. This crate is
an abstraction of this pattern to simplify the repetitive work in
the application.
Read the documentation for more detail.