interop with mainstream grpc

[mediabuff]

https://github.com/cyanfish/grpc-dotnet-namedpipes/issues/2#issuecomment-623641755

Could you please elaborate what makes this "not interoperable" ?

[cyanfish]

Well, first of all, named pipe-based gRPC inherently won't interoperate with socket-based gRPC (which is almost all the implementations to date).

But the point of that comment is that:

• grpc-go supports named pipes
• There are long-term goals to implement named pipe support in grpc-dotnet and others
• But this project won't ever interoperate with those, because they use the (heavyweight, hard-to-implement, but more standardized) approach of running HTTP/2 over named pipes, while this project uses a simple custom protocol instead.

So applications using grpc-dotnet-namedpipes (this project) will only ever be able to communicate with other applications using grpc-dotnet-namedpipes, unless someone goes to the effort of cloning the protocol.

[mediabuff]

thanks for the prompt response. Did'nt realize grpc was hardwired to http/2. Can't interoperability occur at a layer above at the framing level - the frames can be protocol agnostic ?

[cyanfish]

Yeah, it's tied too closely to http2, making use of its bidirectional streaming support among other things. These slides might be of some interest.

[mediabuff]

thank you!!