Since reiZ is going to be very memory intensive, a proper caching system needs to be put in place. This is going to help in the cases where lots of users are browsing the site at the same time.
Requirements for caching to work properly:
Save the HTML either in object or in string form, and keep them in /cache/url-in-question-timeanddate.[ bin? | html ], so they are easily retrievable from the requested URI alone, and can be dismissed if they are too old/expired (cache object lifespan should be adjustable in the backend).
Any page or module should be able to delete their own cached objects (individually and en-masse), as to make sure that new entries are always shown immediately.
There must be both "clear cache" and "enable/disable" function available in the backend. Along with the ability for some users to circumvent the caching (for testing/debugging new functionality on live website etc.), and in extension also excluding certain pages or modules from being cached.
For the cache to be successful, the printed time/dates must be updated via javascript, as not to be perpetually out of date. This will most likely be achieved by inserting the raw timestamps, and having javascript update it on-load (or continually every [specified period of time]).
Preliminary code already added.
Since reiZ is going to be very memory intensive, a proper caching system needs to be put in place. This is going to help in the cases where lots of users are browsing the site at the same time.
Requirements for caching to work properly: Save the HTML either in object or in string form, and keep them in /cache/url-in-question-timeanddate.[ bin? | html ], so they are easily retrievable from the requested URI alone, and can be dismissed if they are too old/expired (cache object lifespan should be adjustable in the backend).
Any page or module should be able to delete their own cached objects (individually and en-masse), as to make sure that new entries are always shown immediately.
There must be both "clear cache" and "enable/disable" function available in the backend. Along with the ability for some users to circumvent the caching (for testing/debugging new functionality on live website etc.), and in extension also excluding certain pages or modules from being cached.
For the cache to be successful, the printed time/dates must be updated via javascript, as not to be perpetually out of date. This will most likely be achieved by inserting the raw timestamps, and having javascript update it on-load (or continually every [specified period of time]).