On 11/04/2013 2:57 PM, Chris Meller wrote:
On Thu, Apr 11, 2013 at 2:14 PM, Matt Read <[email protected]
<mailto:[email protected]>> wrote:
In my plugins scenario I would only be updating the cached_content
whenever content is modified. Storing with no expiry, as I don't
see a need to re-cache it every x hours. Idea being I want to
store the filtered content once, and not run markdown et. al every
page load.
I actually meant expires in the sense that any time content changes it
needs to be refreshed, there probably isn't any value in doing it
automatically at a certain interval. Also remember that any changes in
the active plugins could alter the output of post content: both
activated / deactivated changes, as well as new versions (it could
provide a new filter).
You always complicate things :P
I guess my plugin would react to an activation by triggering a cron job
to regenerate the cache stores. This would be a mighty big hammer for a
small nail. I would be more inclined to provide a regenerate button in
the plugin config or some such, to trigger a cron.
but if content changes, plugins can check if content field is updated
(old value vs. new value) I think. Must check to see if those are available.
--
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
---
You received this message because you are subscribed to the Google Groups "habari-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
