Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

network: Can't have ConnectionState in grpc service #258

Merged
merged 1 commit into from
Apr 5, 2019

Conversation

mzabaluev
Copy link
Contributor

Making service instances to share a ConnectionState was a mistake. The tower-h2 services are not associated with transport connections and can't currently distinguish between connections from which incoming requests are made. See tower-rs/tower-h2#64 for discussion.

Removed ConnectionState::new_listen as we no longer meaningfully can have that in gRPC.

Instances of NodeService (renamed back from NodeServer) get created
for each request by the tower-h2 server.
There is not enough information passed to NodeService on
creation or with requests to distinguish between different socket
connections and manage per-connection state. Which means we need
some other way to identify nodes along with subscription requests.
@mzabaluev mzabaluev requested a review from NicolasDP April 5, 2019 08:06
@mzabaluev mzabaluev added the subsys-network network related label Apr 5, 2019
@mzabaluev mzabaluev merged commit cbd15d4 into master Apr 5, 2019
@mzabaluev mzabaluev deleted the p2p-propagation branch April 5, 2019 08:27
@mzabaluev mzabaluev changed the title network: Can't have ConnectionState in service network: Can't have ConnectionState in grpc service Apr 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subsys-network network related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants