TimeEdit only includes events from the current week and about 3 weeks in the
future. This is not only frustrating for users who want to remind themselves
about previous lectures but it also completely breaks the exam fetcher during
the exam week as it cannot look at the previous events to figure out which
courses you are subscribed to.
The fix to this is to (finally) cache TimeEdit requests. Not only does this
decrease the traffic to TimeEdit and reduce the risk of being rate-limited (or
potentially blocked) but with some more logic you could concatenate old
responses with new ones. Hopefully, the already implemented calendar merger
from the picker could be reused for this.
Using Redis, any calendars from TimeEdit requested during a new week should be
added to the cache. Cached calendars expire after about 4 weeks to match how
far forward TimeEdit allows you to view events. Then the calendars are all
concatenated together and moved to the next step. The cache may need to
support being updated more frequently during the same week to not lose events
being changed on short-notice.
TimeEdit only includes events from the current week and about 3 weeks in the
future. This is not only frustrating for users who want to remind themselves
about previous lectures but it also completely breaks the exam fetcher during
the exam week as it cannot look at the previous events to figure out which
courses you are subscribed to.
The fix to this is to (finally) cache TimeEdit requests. Not only does this
decrease the traffic to TimeEdit and reduce the risk of being rate-limited (or
potentially blocked) but with some more logic you could concatenate old
responses with new ones. Hopefully, the already implemented calendar merger
from the picker could be reused for this.
Using Redis, any calendars from TimeEdit requested during a new week should be
added to the cache. Cached calendars expire after about 4 weeks to match how
far forward TimeEdit allows you to view events. Then the calendars are all
concatenated together and moved to the next step. The cache may need to
support being updated more frequently during the same week to not lose events
being changed on short-notice.