Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Complete
-
Affects Version/s: 3.0.1
-
Fix Version/s: 4.1 RC1
-
Component/s: Redis Support
-
Labels:
Description
This is a feature that could be interesting; the scenario is just this (but the component could be used in similar ones):
- A web service call a method and needs the response that includes some kind of resource identification, assigned when the task starts.
- However the server does not execute the request. The request goes to a Redis Queue using the queue-inbound and queue-outbound adapters.
- So any server will take the message and generate the identification, and then the client should be notified.
My design was based on using a gateway to have the reply channel, and using redis pub/sub facility to block and unblock the calling client, waiting for the ID. But there is not a component to build this automatically; if the server that executes the task send a message over redis I don't find any way of unblock over the gateway and continue.