When rate limits per session kicks in - then the code is essentially given an upper bound on number of refreshes by CoWIN. To improve the odds, we implement checks in between / more frequent than what the ratelimit allows us, using the Public API.
This way - the performance is no worse off than the max capability in the usual protected API method. But just in case the public API lists that slot - we're going to lap it up.
I tested a couple of cases, esp when slots were being released. When slots are being released - this is a hit or miss - it may show availability immediately on the public API, or it may not show up at all (directly being listed as fully booked).
This PR implements an alternate query mechanism as discussed in https://github.com/bombardier-gif/covid-vaccine-booking/pull/449
When rate limits per session kicks in - then the code is essentially given an upper bound on number of refreshes by CoWIN. To improve the odds, we implement checks in between / more frequent than what the ratelimit allows us, using the Public API.
This way - the performance is no worse off than the max capability in the usual protected API method. But just in case the public API lists that slot - we're going to lap it up.
I tested a couple of cases, esp when slots were being released. When slots are being released - this is a hit or miss - it may show availability immediately on the public API, or it may not show up at all (directly being listed as fully booked).
@Nakul93 @6mxo89sqh