You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2022. It is now read-only.
The current script will not allow you to provide a time interval less than 1 minute (was 5 before). Should this be further reduced to something like 10-20 seconds ?
I don't want the cowin-pinger tool to be a cowin API abusing tool as there are a high number of people using this script. If everyone starts to make calls every few seconds it could badly effect the Cowin Portal. I feel 1 minute interval is more than enough but I still wanted your opinion. Comment down your thoughts under this if you happen to see this issue.
The text was updated successfully, but these errors were encountered:
... APIs are subject to a rate limit of 100 API calls per 5 minutes per IP.
So it rate-limits by default.
Meanwhile, CoWIN is running on AWS - CloudFront + WAF + API Gateway. The AWS infra can handle the load, but subject to how CoWIN have built their backed and what redundancies and fail-overs they have added.
Overall, I believe 1 minute is more than enough, because the portal itself is updated occasionally every day. High frequency polling will offer no benefit.
The current script will not allow you to provide a time interval less than 1 minute (was 5 before). Should this be further reduced to something like 10-20 seconds ?
I don't want the cowin-pinger tool to be a cowin API abusing tool as there are a high number of people using this script. If everyone starts to make calls every few seconds it could badly effect the Cowin Portal. I feel 1 minute interval is more than enough but I still wanted your opinion. Comment down your thoughts under this if you happen to see this issue.
The text was updated successfully, but these errors were encountered: