Store feeds in memcached rather than on a filesystem.
Description
Store feeds in memcached rather than on a shared filesystem.
The idea here is not to generate a page and store it in a filesystem but to have the atom.xml generated dynamically (cached by squid as well), with as much of the contents of the feed being cached in memcached.
Functionally I am going to sneak in more works in a feed cached, set the default to be the same as it is right now to display but allow it to be overridden with a parameter.
How to test:
We'd probably want some fairly extensive testing in several feed readers, as well as a DW and tumblr implementation to see if it does anything weird, like duplicate entries between polls. This will have to be a set up, test, post, test, walk away for at least a day, test again because of the inherent time delay in feeds.
Activity
Show:
redsummernight
September 29, 2018 at 4:22 PM
https://github.com/otwcode/otwarchive/pull/2379 is for this issue, it was previously associated with AO3-4502, which became an epic for similar issues. Setting james_ as the assignee and transitioning to "In Review".
Store feeds in memcached rather than on a shared filesystem.
The idea here is not to generate a page and store it in a filesystem but to have the atom.xml generated dynamically (cached by squid as well), with as much of the contents of the feed being cached in memcached.
Functionally I am going to sneak in more works in a feed cached, set the default to be the same as it is right now to display but allow it to be overridden with a parameter.
How to test:
We'd probably want some fairly extensive testing in several feed readers, as well as a DW and tumblr implementation to see if it does anything weird, like duplicate entries between polls. This will have to be a set up, test, post, test, walk away for at least a day, test again because of the inherent time delay in feeds.