[grpc-io] Re: Building a grpc reverse proxy using client headers

> how it can be achieved directly through implementation on gRPC interfaces? Nothing offhand that comes to mind. Probably the original code you leveraged is a good starting point. On Monday, August 10, 2020 at 9:40:21 AM UTC-7 chetan...@gmail.com wrote: > Hi. Thanks for sharing the informatio

Re: [grpc-io] gRPC - node.js simultaneous client calls - reverse ordered

Gotit. Thanks On Mon, Aug 10, 2020 at 11:08 PM Michael Lumish wrote: > I just want to make sure it's clear that the ordering behavior you have > observed here is not guaranteed. Requests made before a connection is > established are not necessarily reversed, the connection state internally > may

Re: [grpc-io] gRPC - node.js simultaneous client calls - reverse ordered

I just want to make sure it's clear that the ordering behavior you have observed here is not guaranteed. Requests made before a connection is established are not necessarily reversed, the connection state internally may change after a connection is established, and requests on the same client may e

Re: [grpc-io] gRPC - node.js simultaneous client calls - reverse ordered

So on the 1st call, while connection is in progress, any subsequent client calls made are stacked up. once the connection is established the call stack is resolved. Just to validate: I made 3 calls after a 1st init call gets resolved as in code below. Prints in the order of 1,2,3 Thanks for your

[grpc-io] Re: Building a grpc reverse proxy using client headers

Hi. Thanks for sharing the information regarding Envoy proxy. I think it will require a lot of changes for me to integrate Envoy proxy in our architecture and writing a simple reverse proxy (if it works) the way I described above is an easier, faster and better option. Do you have any feedback

Re: [grpc-io] gRPC - node.js simultaneous client calls - reverse ordered

Those requests all happen independently. We don't make any guarantees about their order, so the library internals are free to reorder them before sending them out. In this case, the first requests you make after you construct the client object cause it to start connecting, so those requests will be

[grpc-io] gRPC - node.js simultaneous client calls - reverse ordered

Hi, I have started exploring gRPC with Node.js, by basic hello world level client-server js. Code gist snippets and outputs below. I have noticed a strange thing If I instantiate a *client* and call remote function 3/4 times simultaneously, the responses of the calls are printed in reverse or