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.

Sign up for GitHub

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

Jump to bottom

Rush based notification retries #484

Closed

fgalan opened this issue Jul 30, 2014 · 1 comment

Labels

backlog

Member

fgalan commented Jul 30, 2014

Currently, CB sends a notification and if for some reason (e.g. micro-cut in the connection) the receiver is unavailable, the notification is lost.

Thus, it would be a good idea to have a retry mechanism, based on Rush. Rush can be programmed with an HTTP header in order to implement retries.

fgalan added the backlog label

fgalan mentioned this issue

HA issues telefonicaid/fiware-cygnus#92

Open

fgalan changed the title ~~Notification retries~~ Rush based notification retries

Member Author

fgalan commented Sep 27, 2018

It is not realistic at the present point to work on the Rush integration any longer. Thus, issue to be closed.

fgalan closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment