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

Are you planing on putting this on grpc/grpc-dotnet? #2

Closed
taori opened this issue May 4, 2020 · 2 comments
Closed

Are you planing on putting this on grpc/grpc-dotnet? #2

taori opened this issue May 4, 2020 · 2 comments

Comments

@taori
Copy link
Contributor

taori commented May 4, 2020

This package is pretty cool. I just needed some IPC and figured i'll do some research and ran into this. This seems like a great typed alternative.

@cyanfish
Copy link
Owner

cyanfish commented May 4, 2020

Because of the way it's implemented, this package will never be interoperable with any other gRPC named pipe implementation, so it's unlikely to be officially endorsed (I talked about this a bit with jtattermusch).

The long term story for gRPC named pipes is to use HTTP over named pipes. That should eventually be supported in ASP.NET Core, which will let it be implemented in grpc-dotnet.

In the meantime this package should work fine if you don't need that interoperability.

@taori
Copy link
Contributor Author

taori commented May 4, 2020

What a pitty. I particularly like that it does not bind to ports and works the way it does. Thanks for your work in that case! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants