I'm pretty sure there's a memory leak in tapestry because the memory usage climbs and climbs when caching is disabled.
I understand that in a production environment you probably wouldn't want caching disabled, but it seems tapestry should throw out whatever it's creating if it's not going to use them. I don't think this is happening. -Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
