In my use case, always-open gRPC calls / streams are common, where it'd be
idea if they can resume between shorts disconnects (going away).
- Q1: Is there a way that a server would know about the caller's client
going away?
- The client's RPC calls fail later with an error (e.g. Endpoint failed
to read).
- Q2: Can it resume instead? is that configurable?
- Q3: Is there a way to learn that the client / server went away in
the API? heartbeat / ping? -- `channel.watchConnectivityState` takes too
long and only works in the client.
- HTTP2 (the heart of gRPC) doesn't seem to have resumability in mind,
while https://github.com/rsocket/rsocket/ does.
Q4: Could gRPC potentially live on various underlying wire protocols, or
will it be always committed to http2 (
https://developers.googleblog.com/2015/02/introducing-grpc-new-open-source-http2.html
)?
- Q5: [grpc-node
<https://github.com/grpc/grpc-node/tree/master/packages/grpc-js-core>] Is
there a plan for a server impl in Node as well?
- Q6: [grpc-node
<https://github.com/grpc/grpc-node/tree/master/packages/grpc-js-core>]
Any reason to use Node 8.4+ `http2` module over using the `http2` npm
package to make it work on all node versions?
Thanks,
Mostafa.
--
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/af7ea22c-30ae-4311-ae51-6728eb5a7e1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
