Il giorno 29/ott/04, alle 00:03, Brent Johnson ha scritto:
I'm just somewhat concerned about it because it looks like the flowscript is cached while in continuation. So if I'm in a continuation and I change my code.. the change doesnt take affect until I enter the continuation again.. which makes me think that its cached in memory somewhere and over time it may end up sucking up resources.
Yes, having a continuation available will suck up resources. For one thing, all local variables will still be reachable as long as the continuation is valid, so they won't be garbage-collected.
To alleviate this problem, I suggest that you invalidate continuations like this:
var k = cocoon.sendPageAndWait(...); k.invalidate();
Keep also in mind that continuations expire after a timeout that can be configured in cocoon.xconf. So eventually all memory should be reclaimed.
Ugo
-- Ugo Cei - http://beblogging.com/
smime.p7s
Description: S/MIME cryptographic signature
