Hi Jörn, I do not really know that much about FlowScript, but I have been wondering about caching and reloading of flowscripts as well. I do know that there is an entry in cocoon.xconf to configer the js interpreter, look for 'flow-interpreter' and you'll find. 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.
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. > Van: Jörn Nettingsmeier [mailto:[EMAIL PROTECTED] > Verzonden: donderdag 19 oktober 2006 10:06 > Aan: [email protected] > Onderwerp: flowscript caching and evaluation question > > hi ! > > > > the lenya cms provides a usecase framework with a generic > flowscript that allows users to create their own usecases and > views easily without touching javascript *if* their flow > needs are very simple. > > to allow for more flexibility, i would like to add a way for > users to add their own flow code to their usecases. > > it is supposed to work like this: > > the generic usecase handler checks if the user provided a > custom flowscript uri with the usecase configuration > (usecases are Configurable avalon components), which > implements the functions "customLoopFlow" and > "customSubmitFlow" the former is used while the usecase is > "looping", i.e. not yet submitted or cancelled, and the > latter is invoked when user finally submits or cancels. > > it then uses cocoon.load(customUri) to load the custom code. > > the question is: > will the flowscript always be re-evaluated? the sitemap just > says "<map:flow src="genericUsecaseHandler.js"/>, so cocoon > might well think it can cache and/or even precompile the > flowscript once and re-use it. > (my tests suggest that this is indeed the case.) > > the reason i'm using cocoon.load rather than parsing the > customUri file myself and create the custom functions with > "new Function() {}" (which would be guaranteed to be > re-evaluated each time) is that those on-the-fly function > objects are a nightmare to debug because you do not get line > numbers in case of an error. > > how can i solve this? any hints or pointers to flowscript > caching/compiling/evaluation docs (even code) are appreciated. > > regards, > > jörn > > > -- > Jörn Nettingsmeier > > "Hofstadter's Law: It always takes longer than you expect, > even when you take into account Hofstadter's Law." > - Douglas R. Hofstadter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
