Hello, someone wants to use Named Pipes, but still insists on relying on gRPC in doing so (shrugs), so I need your help, as the knowledgeable ones, in clarifying on how feasible it is to make gRPC use Named Pipes instead of network or domain sockets. I am a C guy, so this C++ stuff looks scary for me. I can't get what I need to change. ports are going down to the deepest guts of grpc, from the very start you set ports and then it goes down to the grpc core, where still ports are everywhere.
I am not asking to make a research for me, just an evaluation, since you understand grpc internals and it might be easy to you to answer if changing transport from a network based one to something else is feasible or it would be too hard, since grpc is not flexible with this respect and a bit of direction of where the change should primarily happen - on the surface (API) is enough (doubtfully), grpc core. where? should it be rewritten or it's more an addition? also, I would want to make it in a compatible way, so that code wouldn't stop working with the next gRPC update.
thank you in advance.