You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-101Lines changed: 6 additions & 101 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,9 +36,14 @@ In an `RpcServer`, for each connection, there is one coroutine to read requests
36
36
coroutine to write responses. Requests can be dispatched with a user-defined
37
37
`Dispatch` trait implementation.
38
38
39
+
### Builtin connection pools:
40
+
41
+
-[ClientPool](https://docs.rs/razor-stream/latest/razor_stream/client/struct.ClientPool.html): Auto scalable pool:
42
+
-[FailoverPool](https://docs.rs/razor-stream/latest/razor_stream/client/struct.FailoverPool.html): Fault-tolerance pool
43
+
39
44
## API call interface
40
45
41
-
`razor-rpc`<https://docs.rs/razor-rpc>
46
+
Detail document and example refer to the `razor-rpc` crate<https://docs.rs/razor-rpc>
42
47
43
48
- Independent from async runtime (with plugins)
44
49
- With service trait very similar to grpc / tarpc (stream in API interface is not supported
@@ -47,103 +52,3 @@ currently)
47
52
wrapper
48
53
- Each method can have different custom error type (requires the type implements [RpcErrCodec](https://docs.rs/razor-stream/latest/razor_stream/error/trait.RpcErrCodec.html))
49
54
- based on razor-stream`: Full duplex in each connection, with sliding window threshold, allow maximizing throughput and lower cpu usage.
50
-
51
-
(Warning: The API and feature is still evolving, might changed in the future)
0 commit comments