内容简介:Since the firstTonic was originally released as an alpha because a majority of the crates it depended on were also alphas.
tonic
is a gRPC over HTTP/2 implementation focused on high performance,
interoperability, and flexibility.
It has been a few months since I originally released the 0.1.0-alpha.1
version. Since then there has been a ton of growth and improvements. We’ve seen 32 new
contributors
, two new
guides
, 8 more
examples
and 5
releases
. Not only have we seen a lot of growth internally but we’ve also seen a large amount of adoption.
Changes
Since the first 0.1.0-alpha.1
release, Tonic made several ergonomic changes.
Upgrades EVERYWHERE
Tonic was originally released as an alpha because a majority of the crates it depended on were also alphas. 0.1
signifies that all our dependencies are as lean
as possible.
For instance: syn
and quote
are at 1.0, bytes
is set to 0.5 and hyper
is at 0.13
Thanks to all the maintainers for helping push out all these releases! Also, I would like to note that
cargo-deny
has been very helpful in ensuring that we have no duplicate
dependencies!
Goodbye openssl, hello rustls
The build-in transport module no longer supports openssl
. Instead, Tonic defaults to rustls
, which should simplify building Tonic-based applications and libraries. However, I recognize that Tonic users might want to use a different TLS library, so Tonic supports customization via constructor client
and constructor server
.
Interceptors
Tonic also supports gRPC interceptors (non-gRPC ecosystems might refer to “interceptors” as “middleware”). Like the name suggests, interceptors allow clients and servers to intercept a request and perform an arbitrary action, like adding headers to sign a request or logging a request. See the example below:
#[tokio::main] async fn main() -> Result<(), Box<dyn std::error::Error>> { let channel = Endpoint::from_static("http://[::1]:50051") .connect() .await?; let mut client = GreeterClient::with_interceptor(channel, intercept); // snip } /// This function will get called on each outbound request. Returning a /// `Status` here will cancel the request and have that status returned to /// the client. fn intercept(req: Request<()>) -> Result<Request<()>, Status> { println!("Intercepting request: {:?}", req); Ok(req) }
One key thing to note here is that these interceptors are transport agnostic. They are pure gRPC, it does
not matter where you get the request from, it could be via grpc-web
or http2
.
More examples of this usage can be found
here
.
v0.1.0
I’d like to give a special shoutout to all those that helped the project grow by opening issues, trying Tonic out and opening PRs.
That said, I am super happy to finally release the 0.1
release of tonic
. This is the first stepping
stone in a great ecosystem built on top of
tower
. As always, there is a changelog
and
an issue
tracker if you run into any issues. Please, feel welcome to also join us on discord
if you need any help!
以上就是本文的全部内容,希望本文的内容对大家的学习或者工作能带来一定的帮助,也希望大家多多支持 码农网
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
PHP从入门到精通
邹天思、孙鹏 / 清华大学出版社 / 2008-10-1 / 68.00元
DVD语音视频教学光盘,22小时教学视频录像,全程语音讲解,本书实例源程序、相关素材,本书特色:基础知识—核心技术—高级应用—项目实战,268个应用实例,41个典型应用,1个项目案例,内容极为详尽,实例典型丰富。一起来看看 《PHP从入门到精通》 这本书的介绍吧!