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
{{ message }}
This repository has been archived by the owner on Sep 13, 2018. It is now read-only.
The tokio-proto layer is the easiest way to build servers and clients. All you have to do is handle message serialization; proto takes care of the rest.
It's unclear how to interpret this because it doesn't say anything about the transport layer. The examples are mostly for TCP servers, but I gather that tokio-proto can be used with other types of networking? If so it seems incorrect to say that you only have to handle message serialization.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the "What is Tokio?" doc it says:
It's unclear how to interpret this because it doesn't say anything about the transport layer. The examples are mostly for TCP servers, but I gather that tokio-proto can be used with other types of networking? If so it seems incorrect to say that you only have to handle message serialization.
The text was updated successfully, but these errors were encountered: