[ 
https://issues.apache.org/jira/browse/CAMEL-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220358#comment-17220358
 ] 

Rajasekhar Bhupasamudram edited comment on CAMEL-15751 at 10/26/20, 3:18 AM:
-----------------------------------------------------------------------------

Hi [~dmvolod],

Have completed the changes for the Jiras 15751 and 15754. Could you please look 
into the PR?

Thanks to [~acosentino] for approving the changes.

 

 

 


was (Author: rajasekharb):
Hi [~dmvolod],

Have completed the changes for the Jiras 15751 and 15754. Could you please look 
into the PR?

Thanks to [~acosentino] fro approving the changes.

 

 

 

> camel-grpc - Provide access to stream observer in the camel Exchange
> --------------------------------------------------------------------
>
>                 Key: CAMEL-15751
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15751
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-grpc
>            Reporter: Rajasekhar Bhupasamudram
>            Assignee: Dmitry Volodin
>            Priority: Minor
>             Fix For: 3.7.0
>
>
> Current camel-grpc module provides both the consumer and producer abilities. 
> But, does not allow the camel route to have control over when the responses 
> are sent back to the client.
>  
> {code:java}
> <route>
>     <from 
> uri="grpc://remotehost:1101/org.apache.camel.component.grpc.PingPong?consumerStrategy=PROPAGATION"/>
>     <process ref="myCustomProcessor" />
>  </route>
> {code}
>  
> Consider the above route as an example for grpc consumer (server streaming 
> call).
> In the above, myCustomProcessor can modify the Exchange and set a Message, 
> but if it needs to respond to the client multiple times with a time gap - 
> based on business requirement, using _responseObserver.onNext()_ method 
> calls, then it can't. There is a possibility to collect all the responses in 
> a list and send the list items one after the other. But, if the processor 
> needs to wait for certain amount of time to compute the next response, and 
> then invoke the onNext, it is not possible.
> I think it is a limitation of the camel-grpc component and propose to enhance 
> it by setting the responseObserver as a property in the Exchange object.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to