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
Limit the number of license check and filter update requests #574
Comments
Huh, do we have any notification?:) |
Nevertheless, we should limit the number of any requests to our server. Currently we just do it periodically once in 12 or 24 hours (don't remember then number). The problem is that if our app is killed by Android, timer is started over and first request is scheduled on +5 mins. |
Nope. I think we should make some :) |
Haha, nice:) |
Let's schedule it on v2.7 release. |
@Revertron not this issue, make a separate one. This one is renamed to "Limit the number of license check and filter update requests" |
Ah, okay. |
My 2¢: If y'all don't mind (especially since #611 will probably increase server load some, anyway), but even 12 hours is probably too long an interval for a manual check. I can sometimes request a filter update 1 hour apart from my last 1, & get an update to several lists. (The English & German lists seem to have frequent updates!) Limiting the automatic checks _only_ would be my preference. |
@TPS I mean the periodic automatic update check, manual checks have no limitations. |
Done! |
Currently they are too irritating with ~5 notifications a day.
Original request:
https://forum.adguard.com/index.php?threads/adguard-%D0%B4%D0%BB%D1%8F-android-%D0%91%D0%B5%D1%82%D0%B0-%D0%B2%D0%B5%D1%80%D1%81%D0%B8%D1%8F-2-6-23.10581/#post-83803
UPD: we don't have any "license expiring" notifications (why so btw?). So in this issue we'll do another useful thing: limit the number of license check requests.
Usually we do such request once in 12 or 24 hours. The problem is that currently when app is killed and restarted, timer is started over and first license check is scheduled on +5 min.
The text was updated successfully, but these errors were encountered: