Yes, this is possible. You'll need to implement some unpacking scheme on L, but it can then forward the raw bytes of the request. Note that if you are using Proto, you may not be able to use all the generated stub code. If C, L, and R all know about the same message types, then you can use the proto stubs.
Note also that the headers will need to be captured from C->L, and the response trailers from R->L. If you wanted this to be "delayed" in any way, it may get more tricky. On Sunday, January 13, 2019 at 12:52:29 AM UTC-8, [email protected] wrote: > > Consider a grpc client C, and servers L & R (local & remote). > Servers L & R are connected. Client C can reach only server L. > > Client C needs to send a request to server R. > > Can I create a "relay_request" message that server L will support, where > the body is the request to send to server R? (also dealing with relaying > the reply) > > Is there anything better I can do for such a scenario? > > Thanks, > Dan > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/fc766ee0-a9b7-46f2-bbd5-024c1fba3e1a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
