I've been thinking through the process of caching zones for quicker
cpu processing, and envision a process like this:

1) When a call is made to do the markup for a zone and zonecache: true
is set in site.config, then a simple check is made to see if a cached
version exists. If so, it returns that cache. Done.  Perhaps it should
also check to see if zone cache is newer than the actual zone page.
And that no action is set.

2) If zonecache page not returned, the zone page is retrieved, markup
processed, etc.

3) If zonecache: true is in site.config, the appropriate zone page is
saved/updated in a 'zonecache' directory (or zones, or cache, or
something).

4) The html for the zone is returned, and the next zone is processed.

Problems:

1) There needs to be a way to disable caching for pages that have
dynamic content, or a form.
My thought is to create a [(nocache)] markup on pages that should not
be cached. Would only affect that specific zone page. Probably would
work by setting some global variable that would be checked before
saving a new cache.

2) There needs to be a way to update a zone cache when a page is edited.
My thought is to have an action page that deletes any cached zones for
a given page. They would be instantly updated unless the page had a
[(nocache)] markup. Actually, not sure this is necessary given how the
ideas above are lined up.

Anyway, this could be very easy to implement and should dramatically
increase page build speed. Just thinking out loud. Looking for
feedback, before I dive in...

Cheers,
Dan

P.S.  It might be interesting to store the zonecache's in a simple
database for even faster recall. Could be a cool idea.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
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/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to