On Thu, Jan 16, 2003 at 04:40:07PM -0600, Christopher L. Everett wrote:
But again, there is the issue of mapping changed data onto dependent
pages. I guess one way to do that is to track which database rows
appear in which pages in the database. Since typically I do several
database
I'm moving into the XML space and one of the things I see is that XML
processing is very expensive, so AxKit, PageKit, et al make extensive
use of caching. I'm keeping all of my data in a MySQL DB with about
40 tables. I'm pretty clear about how to turn that MySQL data into
XML and turn the XML
On Thu, Jan 16, 2003 at 06:33:52PM +0100, Honza Pazdziora wrote:
On Thu, Jan 16, 2003 at 06:05:30AM -0600, Christopher L. Everett wrote:
Do AxKit and PageKit pay such close attention to caching because XML
processing is so deadly slow that one doesn't have a hope of reasonable
response
Christopher L. Everett wrote:
But I haven't
been able to wrap my skull around knowing when the data in Mysql is
fresher than what is in the cache without doing a major portion of the
work needed to generate that web page to begin with.
There are three ways to handle cache synchronization:
1)
Perrin Harkins wrote:
Christopher L. Everett wrote:
But I haven't
been able to wrap my skull around knowing when the data in Mysql is
fresher than what is in the cache without doing a major portion of the
work needed to generate that web page to begin with.
There are three ways to handle
Christopher L. Everett wrote:
I see where one could combine polling and invalidation, for instance
by having empty files representing a page that get touched when the
data for them go out of date.
More commonly you would combine TTL with invalidation. You use
invalidation for the simple
