hi all,
I'm nearly done with a version of the Page class that can cache page output.
If I have time today, I'm going to extend that to support caching of
individual module output as well.
This is going to require a lot of testing to verify that the right material
is presented in all circumstances, but I'm seeing nice performance gains on
crappy debug-laden code already. (And, it's cool) :)
Right now, I'm generating page cache ids with:
-Request URI (that includes the get string)
-A defined variable name (from the page definition)
-The value of that variable.
Cache Ids are an MD5 of that string. I think that works pretty well for
pages, I'm trying to decide what I want to enable for modules.
If anyone has suggestions for "caching parameters" they'd like incorporated,
please let me know asap as I'm writing the code today...
I'll check it in as soon as I've cleaned up some of the more ick debug
things I have floating around in it.
PEAR Cache is elegant, easy to use, fast as hell, and after some stupid
include path problems, working perfectly. I'm quite happy with the import
scheme, as well.
If you're building modules, I encourage you to take the time to look in
binarycloud/ext/pear/ - and make use :)
best,
_alex
--
alex black, ceo
en...@tu...
the turing studio, inc.
http://www.turingstudio.com
vox+510.666.0074
fax+510.666.0093
|
