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
When one application sends a message to another, it may be interested in receiving a reply - a two-way conversation. For example, if I send a command I might expect to receive a "success/failure" message in response.
In order to support this asynchronous request/response pattern in JustSaying, the receiving application needs to know where to send the response message to. This could probably be accomplished by using a well-defined "reply to" property on the command message indicating, for example, the SQS queue to which the response should be sent. Or perhaps we could define an SQS message attribute to convey this.
Either way, providing first-class support for this pattern in the library would be useful for clients, allowing them to implement this pattern with minimal setup.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
When one application sends a message to another, it may be interested in receiving a reply - a two-way conversation. For example, if I send a command I might expect to receive a "success/failure" message in response.
In order to support this asynchronous request/response pattern in JustSaying, the receiving application needs to know where to send the response message to. This could probably be accomplished by using a well-defined "reply to" property on the command message indicating, for example, the SQS queue to which the response should be sent. Or perhaps we could define an SQS message attribute to convey this.
Either way, providing first-class support for this pattern in the library would be useful for clients, allowing them to implement this pattern with minimal setup.
The text was updated successfully, but these errors were encountered: