Re: [Zope-dev] Declaring Dependencies for XML documents (Was: HowTo Improve Cache Coherency for RAM/Disk Cache Manager...?)

2003-03-04 Thread Andy McKay
Anyway, after talking this over with my colleague, I realize that
the problem of *deriving* dependencies is fundamentally undecidable.
We might be able to figure it out in the case of simple acquisition,
like
span tal:replace=here/aObject/aMethod/
But it is hopeless for pure python:
span 
tal:replace=python:I-can-do-anything-and-you-cant-stop-me(REQUEST)/
:)
Well you could, in theory, hook every object as CallProfiler does and 
then you would know for each request what object was called and Cache 
it. You could even do something really clever like using CallProfiler 
automatically cache objects that took longer than a certain amount of 
time...

But there are more issues with that than there are days in a year and 
you could be writing that code forever, letting the user figure it out 
manually is an easier choice.

Cheers.
--
  Andy McKay
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Declaring Dependencies for XML documents (Was: HowTo Improve Cache Coherency for RAM/Disk Cache Manager...?)

2003-03-04 Thread Paul Winkler
On Tue, Mar 04, 2003 at 02:32:31PM -0500, Shane Hathaway wrote:
 Ah, but you might have something there.  What if there were a cache 
 manager that simply dropped its contents whenever anything changes in 
 ZODB?  You could associate nearly all scripts and templates with that 
 cache manager without any fear of stale cache entries.  For many sites, 
 it could be an instant win.

interesting idea. there's certainly plenty of sites, though, where
the cache would get invalidated so often that the cache would be
of limited value.  e.g. a busy squishdot-type site, or many CMF sites.
and on those kind of sites, the busiest times are when you most need
the cacheing...

but the simplicity is certainly appealing...  and in my case, i 
have a CMF site where this would likely be quite useful since
the public never logs in, only our content management team, and
we tend to make changes on dev servers and push them to production
in a big bunch.

-- 

Paul Winkler
http://www.slinkp.com


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )