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

Reconnecting mode is too sensitive when requests are failed #235

Closed
algorys opened this issue Feb 13, 2018 · 1 comment
Closed

Reconnecting mode is too sensitive when requests are failed #235

algorys opened this issue Feb 13, 2018 · 1 comment

Comments

@algorys
Copy link
Collaborator

algorys commented Feb 13, 2018

The reconnecting mode is too sensitive when requests are failed inside App client. Currently, App goes into reconnection mode after 2 errors on GET and 1 error on POST and PATCH.

Maybe App should have a counter and try to reconnect only when that counter reaches a certain number (for example 10).

Waiting for alignak-backend-client #26 to be solved too.

algorys added a commit that referenced this issue Feb 27, 2018
algorys added a commit that referenced this issue Feb 27, 2018
@algorys
Copy link
Collaborator Author

algorys commented Feb 27, 2018

Now that App can run without internet connection and autodetect if backend is connected, there are still some adjustments:

  • Improve start of App: thread are launched one by one at start. Threads at start should be launch together.
  • Login Window should quit App, if user if user click on window cross !
  • History for an host can be replaced when user look for an other host in App. ThreadManager should manage this kind of thread in a separate way.

algorys added a commit that referenced this issue Feb 27, 2018
algorys added a commit that referenced this issue Feb 27, 2018
Ref #235 Improve App start, fix Unit Tests for AlignakApp class
This was referenced Feb 27, 2018
algorys added a commit that referenced this issue Feb 27, 2018
algorys added a commit that referenced this issue Feb 28, 2018
@algorys algorys mentioned this issue Feb 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant