gRPC c++ multiple outstanding requests
<p>I have a server/server app, where one server looks much like a client but is servicing requests from a client -- so I'll call it a client. There are several different rpc messages, lets call them resolve, bind, unbind. I'd like the client to be able to freely send resolve, bind, and unbind requests asynchronously, eventually getting responses. Do I need to use different channels for this (hope not), do I need to stream each -- that seems a bit odd as I'd like to be able to send resolve, bind, and unbind (with their payloads) free of having to wait for responses. Yes, I'll eventually process the responses (but at my leisure), generally only as part of cleanup or to forwarding to the real client. Is this reasonable using gRPC, do I need different channels, do I mark them all as (stream request-type) returns (stream response-type), or do I do something different?</p>