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

Push signals to RabbitMQ #15

Open
2 tasks
cdparra opened this issue Aug 8, 2017 · 2 comments
Open
2 tasks

Push signals to RabbitMQ #15

cdparra opened this issue Aug 8, 2017 · 2 comments
Assignees

Comments

@cdparra
Copy link
Member

cdparra commented Aug 8, 2017

In a nutshell:

  • We need to make sure we are pushing signals to RabbitMQ. An option to map signals to RabbitMQ is:
    1. Push signals to an exchange called appcivist
    2. Each resource space should be related to a queue (identified by its uuid)
    3. Use routing keys to route to the proper queue
  • Let's document how are we pushing these signals to RabbitMQ (if we are) to facilitate the task of reading these push notifications from the UI. Create a Readme file inside /docs/ folder

Obs.: This is probably done better in the subscription-manager

@cdparra cdparra added this to the 201708 Sprint 3 milestone Aug 8, 2017
@cdparra
Copy link
Member Author

cdparra commented Aug 8, 2017

Maybe not needed if we can read directly from rabbitmq queue

@cdparra cdparra removed this from the 201709 Sprint 4 milestone Sep 19, 2017
@cdparra cdparra changed the title Binding component to read notifications for the UI Push signals to RabbitMQ Dec 3, 2017
@cdparra cdparra added this to the 201712 Sprint 1 milestone Dec 3, 2017
@cdparra
Copy link
Member Author

cdparra commented Dec 22, 2017

I think we have covered this on slack: we will use user uuids or ids as rabbitmq exchanges/queues

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

3 participants