Artem Bilan

@zhongyang0316 , What made you to close the issue? The fact that we don't do anything here doesn't mean that we are against such a feature. So, I'll reopen it...

Well, have just bumped into this article from Twitter: https://medium.com/netifi/differences-between-grpc-and-rsocket-e736c954e60 So, quoting the first paragraph: > We get asked about this all the time. In general, gRPC and RSocket attempt...

@tsathishkumar , Thank you for sharing that with us. Only the point of this issue that we really talk about Channel Adapter implementations for Spring Integration: https://spring.io/projects/spring-integration

Thanks, @meltsufin , for feedback! Does it mean that there is just enough to use existing `HttpRequestExecutingMessageHandler` and `HttpRequestHandlingMessagingGateway` with the mentioned `ProtobufHttpMessageConverter` to communicated over gRPC protocol?

Thanks. That makes sense. So, we indeed need something what really connects and sends & receives Protobuf messages over gRPC. I need to dig more then how to build server...

Yeah... OK. So, there is no a generic way to interact with gRPC with some *message* abstraction, like we do with `WebServiceTemplate` in Spring WS for SOAP? What you say...

OK. Great! So, technically we don't need to go a generic `ClientCall` "hardcore", since a regular stub generation would bring us the same behavior. It is really much better to...

Well, I would stay away from such a feature since that `inputChannel` is really about a bean reference. Let's see if existing workarounds are OK with you before going deep...

Since you didn't show the body of your error handler, I also did not in my `.handle()`. Technically you still can have that method and you can call it like...

Closed as `Won't Fix` with respective explanation above.