Michael Lumish

In your example JS code, you interact with both the request and response objects using camel case field names, so that is consistent. And that is actually not what happens...

Thank you for moving this. I think this is an interesting idea that is worth exploring, but there are also some complications you haven't addressed. On the client side, these...

Three or four different approaches for using async/await with gRPC have been suggested in this issue so far. I am going to officially recommend that you use one of those....

It's not really clear to me what an observable-based API would look like, so I can't tell how effective it would be at solving the problems I brought up. In...

As I stated in my first comment in this thread, if someone is willing to write up a proposal that solves the problems I brought up, preferably without breaking the...

First, as mentioned in my first comment, the "proposal" I was asking for something more fleshed out that follows the format in [the gRPC proposal repository](https://github.com/grpc/proposal). In addition, you say...

I'm still not following why you would want to connect getting the response as a promise to finishing writing to a stream. It seems to me that the user could...

Writing the request messages and setting up a handler for response messages are independent actions. In the current unary and client streaming APIs, the callback to handle the response is...

The server may refuse to serve new requests if it is already handling too many other requests. This is normal behavior. Your client code will need to be able to...

I would like to fix this, but I don't understand what might cause it, so I have some questions: 1. What gRPC server implementation is your client communicating with when...