Stepan Koltsov

Probably better option would be making TLS implementation optional in native-tls crate. I've [created a feature-request](https://github.com/sfackler/rust-native-tls/issues/33).

Patch welcome.

@siddontang multithreaded event loop with futures-mio-tokio is an area I haven't started exploring yet. However, at this moment grpc-rust lacks a lot of simpler performance fixes, the most important are...

@repi no, grpc-rust is fully concurrent. If `server.http.set_cpu_pool_threads` is specified, server callback is executed in the thread pool, which is useful for synchronous processing (e. g. for synchronous I/O). However,...

@Kane-Sendgrid I didn't look at latest tokio, AFAIU it's unreleased right?

@repi again, I'm not sure I understand. The client is also fully concurrent. The client can execute multiple concurrent requests. The client can be shared by multiple threads. However, the...

I think upgrading to the latest stable rust will fix the issue.

Yes, it should be upgraded. It is not trivial, because last time I tried, something was broken in openssl related to ALPN.

There is no plans, and I'm super busy now to maintain the project. Sorry. If there are PR's I will try to review and merge them.

Neither gRPC nor protobuf designed to handle message of size 4G. gRPC protocol message length is encoded in 4 bytes (thus cannot exceed 4G). Although protobuf does not explicitly limit...