-
Notifications
You must be signed in to change notification settings - Fork 40
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
Use ETag and If-Not-Modified #120
Comments
Note to myself: |
We need to be careful with Opencast's handling of ETags together with the use of the cutoff parameter. Cutoff may limit data received and following requests will return a NOT MODIFIED while not all data have been transmitted. |
So as I understand it, Opencast should only return NOT MODIFIED only if the calendar has not changed in any way since the last request. So there shouldn't be an issue combining cutoff with ETags? Seems like the worst-case scenario is a false-positive, i.e. if you request with a cutoff date of 7 days ahead, and the calendar has modified because a recording was added 10 days ahead, you could still get a whole new calendar for the next 7 days even though it's not necessary. But that's still better than getting a new calendar on every request. |
In Opencast 4.x getting a calendar is a relatively expensive request, even an empty calendar as in the example below which takes 2.2s db query time to produce zero rows. So for pyca with OC 4.x, using ETag / not-modified is an important optimization for CAs.
|
To reduce load for the Scheduler…
The text was updated successfully, but these errors were encountered: