You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Unwrap String in request-reply when reply is a String [\#11](https://github.com/reactive-commons/reactive-commons-java/issues/11)
53
+
- Tolerant reader in all message receivers [\#10](https://github.com/reactive-commons/reactive-commons-java/issues/10)
54
+
- Integrate acceptance test with travis. [\#7](https://github.com/reactive-commons/reactive-commons-java/issues/7)
55
+
- Query handler returning an empty publisher causes timeout on the receiver [\#1](https://github.com/reactive-commons/reactive-commons-java/issues/1)
56
+
57
+
58
+
59
+
\**This Changelog was automatically generated by [github_changelog_generator](https://github.com/github-changelog-generator/github-changelog-generator)*
The return type of the QueryHandlerDelegate should be Void
808
+
</td>
809
+
</tr>
810
+
</table>
811
+
</div>
812
+
<divclass="paragraph">
813
+
<p>This second interface allows the request / reply pattern not to have to be resolved in the same flow. For example,
814
+
when the execution of a task is requested, and it can be processed by a group of workers, who leave the result in a database. There is another group of workers who are in charge of listening to the changes in the database and responding to that request. In this scenario, the process who receives the request is not the same process who responds to it. That is the usage scenario for QueryHandlerDelegate:</p>
<p>When the report creation task is completed, the process responsible of responding should call the reply method of DirectAsyncGateway passing the from object like this:</p>
0 commit comments