On 29 Dec, David N. Welton wrote:
> Personally, I don't see much of an advantage to doing this. Pages get
> bytecompiled and cached the first time they are hit, and stay byte
> compiled for subsequent requests, as long as there is enough space in
> the cache, and the file on disk doesn't change. The extra hassle of
> having compiled pages sitting around isn't worth it, IMO.
I supposed dtcl destroyed ::request after executing the page - so I don't
see how it could be stored bytecompiled? But I could be wrong here. I
supposed it stored the +>abc<+ -> hputs "abc" version but I can't see how
it stores bytecompiles. I suppose I'd better browse thru the code again :>
... and see if the cookie code got finally fixed in the cvs version ;-)
--
Wojciech Kocjan
email [EMAIL PROTECTED]
mail->sms [EMAIL PROTECTED]
www www.zoro2.org
tel +48-501-778778
PGP signature
