Yup -- agreed, default has to be no-caching to be backwards
compatible. I think that's how the code works -- at least that was
my goal but I could have screwed it up :) I'll take a look.
-Jim
On Jun 25, 2005, at 10:20 PM, Dossy Shiobara wrote:
On 2005.06.25, Jim Davidson <[EMAIL PROTECTED]> wrote:
* ADP improvements including:
-- A new execution caching technique at the ns_adp_include level
[...]
Embedded ns_adp_include's with the -nocache flag at lower levels
allow
you to still execute dynamic code within cached blocks if necessary.
[...]
While I think the idea that "upgrade to 4.5, and your ns_adp_include's
will be cached," I think it's critical that the *default* behavior be
backwards compatible, i.e., without any code modification,
ns_adp_include does NO caching.
Looking in nsd/adpcmds.c and nsd/adpeval.c, it looks like ttlPtr is
NULL
if you don't explicitly pass a "-cache ttl?" arg to ns_adp_include,
which I assume implies "don't cache" - but cache == 1, which looks
like
it leads to different behavior than if you pass -nocache, which sets
cache == 0.
The reason I think it's important to preserve backwards
compatibility is
that in order to take advantage of caching, application code will
likely
require modification: at that time, one can make the change to the
relevant ns_adp_include calls to specify "yes, the target is safe to
cache." I could be wrong here, but my experience dealing with
Vignette
(which has had this functionality for a long time) leads me to believe
otherwise.
...
I guess I need to spend more time re-reading all that code until I
either (a) understand it completely, or (b) understand it enough to
change it to be simpler. :-)
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
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.
--
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.
