Support HTTP Etags for frabxml/ical/... exports #492
Closed
Comments
I'm assuming you mean the exports, not the API? |
Nice. Thank you for the quick action. |
Yeah, that is correct. You can be sure the change will be included in all instances running the upcoming 0.8 release and above, soon.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem you are facing
Client applications which retrieve the schedule data from an Pretalx instance do need to load the file everytime. This increases the traffic for both the server and the client.
Possible Solution
The Pretalx API should be able to provide and consume HTTP ETags.
Context
I am maintaining the EventFahrplan project which consumes schedule data from the Pretalx API.
The current EventFahrplan implementation compares the old and the new schedule to find out whether it has changed. This could be done by the server using ETags.
The text was updated successfully, but these errors were encountered: