Dossy Shiobara said:
> This really ought to be a server-wide cache sitting in
> servPtr->adp.cache rather than itPtr->adp.cache ...
I would think so! :) The problem with that still is that it is not
persistent, which could mean that if you restart your server under high
load, all the cache generation that takes place could overwhelm it, while
under normal circumstances it's perfectly happy. (plus it can become a
memory hog!)

Although that problem shouldn't be part of Jim's ADP caching, but the
underlying ns_cache could be modified to support caching to the file
system, which you can specify wether you want it or not when putting
something in the cache. (with a, ehrm, cache of the cache in memory so
popular content is very fast, but with a limit on memory usage, so the
server doesn't keep growing) Put that cache on one of them ATA-RAM PCI
cards with backup battery and the whole thing will work like lightning!

> I think the key (should be) a Tcl list, with elements being the full
> path to the ADP plus all the ADP args.  I'd have to re-read the new code
Sound like how I would do it, yes.

> [ns_cache_flush] should work.
That can't do a cluster wide clear, can it? Another "someday" feature to
be added to the list! :)

Cheers,
Bas.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to