I have an application where the client establishes a bidirectional connection to the server, and the server begins sending requests to the client and vice versa. This app runs jobs, so that once a job starts, the messages flow back and forth from server to client and client to server. I would like to gracefully deal with exceptions thrown from the client. I'm not entirely sure if I should be calling onError for non-critical errors, or if I create a new Error message type and send via onNext. If I use onError, then the client needs to re-connect with a new Channel -- What is the better way to deal with this problem? Is there another way?
Related question - for the Java impl of gRPC - is it possible to have the server log the stack trace of an error sent by the client via onError? I'm setting the cause on the io.grpc.Status instance, but it doesn't seem to be available on the receiving end. Thanks! - Matt -- 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/a7948518-75d1-425e-8699-81508c643b14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
