Lucio Franco

What @davidvartan suggested works, there are ways you can manually build a router to serve both on the same socket. This would require you to detect the incoming path. Mostly...

@GeorgeHahn you probably want to do something like this https://github.com/toshi-search/Toshi/blob/master/src/cluster/rpc_server.rs#L29 This is how we type alias the client in toshi. Which then allows us to pass it around.

The codegen currently does this for the server here https://github.com/tower-rs/tower-grpc/blob/master/tower-grpc-build/src/server.rs#L313 What is your use case for the client side? iirc you shouldn't have to worry about this when generating codegen...

@dckc currently, there is a maybe broken in progress PR for async/await grpc but we have some big plans around this and will be changing a good amount. Its not...

@thedodd I believe this pattern actually belongs in something like the base tower repo, as you can abstract the recognizing part and be abstract over services. Though we are still...

I believe the latest master should be building fine here, do you know what issues you are seeing specifically? @spacejam

Initial work is being worked on here https://github.com/tower-rs/tower-http/pull/19

@hrydgard Hi! So the issue here is that they are under the same package. The issue is that the codegen currently does not have knowledge of the other services and...

@hrydgard Ok that work around seems fine, pretty much either change will have to make a large change to tower-grpc-build (which is nasty right now due to codegen) or change...

@hicqu hey! So I am curious if the reduction comes down to the contention that may exist within `h2`? As of now, I don't think we have any plans for...