Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe mechanism used when receiving response #67

Open
pdemarti opened this issue Apr 19, 2021 · 0 comments
Open

Describe mechanism used when receiving response #67

pdemarti opened this issue Apr 19, 2021 · 0 comments

Comments

@pdemarti
Copy link

pdemarti commented Apr 19, 2021

This looks like a very interesting project, one that would replace some custom code we have where we create actual SQS queues for each requester (so as to send the responses to the correct requester).

Unfortunately, the projects where we need this are all in Python, and we don't want to add dependencies to py4j or the like.

Your documentation and the introductory post give some clues about the overall mechanism:

when sending a message, the virtual queue name is attached as an attribute to the message;

Ok, I can understand that, and how the receiver would then use the same attribute when sending the response. But when receiving a message, what is the mechanism actually used (on the real SQS queue) to filter messages for the requester?

BTW, my assumption is that we have distributed requesters; is that correct?

It would be good to provide some explanation about the underlying mechanism that is used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant