Ok thanks for the responses, i indeed have a memory leak but it's probably my own code. I had an application made entirely of forms to do, and i think i misused cocoon... (cforms couldn't do it so i ended up with various xsl layers to "feed" the forms, from the db and from xml, but as the client refined his requests and wanted more and more specific things for each form, i ended up with a huge bloat... )
----- Original Message ----- From: "Tony Collen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 20, 2004 9:21 PM Subject: Re: flowscript and infinite loops > Arthur van Dorp wrote: > > >> Remember, the execution is halted at sendPageAndWait(), so nothing is > >> really "running" at that point. Only when <map:call continuation=""/> > >> is called, will the execution resume. > >> > >> If the user clicks on a different link and "loses" the continuation > >> ID, the continuation will still be around (i.e. it can be restarted), > >> until it expires and is cleaned up after a while by the > >> ContinuationsManager. > >> > >> If you managed to keep track of the continuation IDs, the user could > >> even switch back and forth between the loops. > > > > > > I think the question is more about memory consumption. Isn't it? > > > > Yeah, I guess I forgot to mention that part. I would guess the > ContinuationsManager would clean it up and there would be no memory leak. > > Tony --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
