|
@lucio_d_franco | |||||
|
And next up is tonic 0.1.0-beta.1 is out! This release is big, lots of changes, including a few breaking :) The big highlights tokio 0.2, hyper 0.13, no more openssl, custom connectors, and initial server tracing support!
Check it out!
github.com/hyperium/tonic…
|
||||||
|
||||||
|
Lucio Franco
@lucio_d_franco
|
19. pro |
|
One thing you may notice is that this is a beta.1 release but not a full 0.1 release. We are waiting on one more breaking change to happen and that is for prost 0.6 which will come with full bytes 0.5 upgrade and a few others.
|
||
|
|
||
|
Lucio Franco
@lucio_d_franco
|
19. pro |
|
Currently, we use a bit of a hacky method to interop between bytes 0.4 and 0.5 but this will go away by 0.1. I am hoping that 0.1 will follow up very soon!
As always let me know if you run into any issues!
|
||
|
|
||
|
🦀 shady khalifa
@ShekoHex
|
20. pro |
|
Very Cool 😎
but I have a little question, could tonic be a (framework/runtime)-agnostic? I mean the way that we could use it with any tokio-like framework? for example the async-std?
|
||
|
|
||
|
Lucio Franco
@lucio_d_franco
|
20. pro |
|
Tonic is totally runtime agnostic, the transport module is the only thing tightly coupled to tokio. There are abstractions in place that allow you to swap out the http2 implementation easily. I just don't have the time to maintain a http2 implementation that works with async-std.
|
||
|
|
||
|
Justin Guidroz
@justin_guidroz
|
20. pro |
|
@carllerche Impressed so far with Tonic. Has simplified a gRPC client from the current one written with tower-grpc.
|
||
|
|
||