-
Notifications
You must be signed in to change notification settings - Fork 214
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
A trick to avoid caching #487
Comments
This is cool, I think we can do this. However, since this is already public, do you see a patch coming from cowin for the same soon? |
Why do they want to Cache data for UI ? doesn't make sense at all.. |
I noticed this last night while doing some testing. |
Yeah thats the annoying part they probably might release a patch to fix this |
Even with our current script caching doesn't seem to be a problem if we are using findBy* APIs. Today I tested for almost 3hrs with 7secs refresh rate and was able to book when slots opened up (it was faster than telegram alerts) |
Can some one try this out? I stopped getting OTP suddenly so unable to test it end-to-end. |
Tested it, seems to work fine. Does this change the date format on every API call? |
Ya it rotates it. |
Have you also raised a PR? I'll test it out. |
I guess it's failing, which find option you used ?? |
@shivaslifzz find by date option for district |
Well, I don't think this idea is worth raising the PR. Currently, find by is super strong and this calendar is still bad. We are still restricted by 20sessions. |
Agree with @6mxo89sqh, for now find by option is perfect. But in future if this was to change then we can use this alternative as a fix. |
have you tried this with public APIs? |
So I just found this video on youtube which explains how we can change the format of date to avoid getting cached data. I think it would be great if we could integrate this in our code.
What are your thoughts guys?
https://www.youtube.com/watch?v=hf44_-qqddY
The text was updated successfully, but these errors were encountered: