-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Buffer the device/folder rejected messages so the GUI gets them even when connecting later #4084
Comments
Yes, we should probably do something about that. |
One way to solve this today would be to set up a separate subscription for the relevant events only and have the GUI poll that. |
This should probably be turned into a persisted in config thing to survive restarts and add free deduplication. |
Maybe. The separate subscription mentioned above is implemented(-able) today though. That gives you a thousand event buffer for just these types. |
Sure, yet it does not deduplicate (which all the clients have to implement), nor is it persisted between restarts, which it probably should be. |
Fixed by #5084 |
When launching the GUI, Accept/Refuse new device or folder won't show immediately although many other infos are displayed.
Could it be possible to have the core to store such requests in RAM (until the source stops its request) and have them passed to the GUI on launch (or have the GUI on launch to question the core for such recent requests)?
The text was updated successfully, but these errors were encountered: