Hi maintainers, This is probably not the first time you heard the request to support named pipe in windows. Can you provide some kind of an official answer if this is something that you are going to support ? I understand from the mailing list that the TCP transport implementation is stable and you are happy with it, but you are still open for other implementations.
If the answer to the first question is no, does the interface of adding a custom endpoint is the right way to do that ? If yes, can I get guidelines of how to add a new endpoint ? Is there an option to change the endpoint at runtime ? I need that one process in my application will use both options, one time using TCP socket and other time with windows named pipe handle. Another question is regarding the new experimental interface AddExternalConnectionAcceptor, is that is some kind of alternative for what I am looking for ? Does it means that I can create any kind of a connection outside of the gRPC core and then attach it to the core ? If this is true then I can implement a pipe server/client, make a connection between the client and server, and then send RPC through the gRPC core on that connection. If this will work then I do not need to make any changes to the gRPC core. Thanks, Gal. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/1da55fa8-38cd-4e4d-8d51-2bf2dca3a21f%40googlegroups.com.
