> iiuc, i can configure it to check the flowscript for > modification each time (at a performance penalty). but how > does cocoon determine "modification"? if it only looks at the > file timestamp, i still have problems, because i have the > parameterised "cocoon.load" call in there - which means that > the cache is only valid if the flowscript *and* all > cocoon.load()ed resources are unchanged.
Yes, setting reload to true makes Cocoon check file stamp, though with a delay of xxx milliseconds if you specify a number (one of the other parameters). Dynamically loading code might not work as expected, though if you put the cocoon.load() *inside* a function, it might work afterall. > are there docs on cocoon.load()? Really dunno. Ask on cocoon-dev or try reading the code.. :-P > > I also know > > that there is something special about continuations. It's a weird > > situation if you request a continuation, but your script has been > > changed in the meantime. I believe continuations are > invalidated for > > that reason if something like that occurs. > > eek. looks like i have to ditch my current approach with > cocoon.load() and use dynamically generated function objects then. Not sure, but make sure to test thoroughly! :-) Kind regards, Geert Drs. G.P.H. Josten Consultant Daidalos BV Source of Innovation Hoekeindsehof 1-4 2665 JZ Bleiswijk Tel.: +31 (0) 10 850 1200 Fax: +31 (0) 10 850 1199 www.daidalos.nl KvK 27164984 De informatie - verzonden in of met dit emailbericht - is afkomstig van Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden ontleend. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
