Hi Filip, thanks for adding semantically meaningful names to the classloaders. That is certainly very useful. I've not yet delved into the interactions of the current Tomcat session manager with Terracotta, but it sounds to me that your idea of a lazy map is an idea worthwhile to pursue. The public API that will be published will however not be useful for that I think. It's mainly focused towards programmatic configuration and JMX, if I recall correctly. Juris, could you please correct me if I'm wrong or missed an episode? As far as my knowledge of the Terracotta internals stretches, that lazy map wouldn't be terribly difficult to implement, but it does require familiarity with the internal APIs and concepts. I suggest that you submit your idea as a JIRA issue so that we can keep track of it and maybe schedule it for a future release.
Thanks for your interest and contributions. Best regards, Geert On 17 Aug 2007, at 23:58, Filip Hanik - Dev Lists wrote: > Hi all, > In Tomcat 6.x (trunk) we have added in names to all the > classloaders in > Tomcat > Names are > common > shared > server > For the top level loaders. > > And for the webapp classloaders, the name is > Engine.name#Host.name#Context.name > > For example > Catalina#localhost#/probe > > And for the ROOT context, it would be > Catalina#localhost# > > Since the name of that context is "" > > This should bring us one step closer, I haven't forgotten that it > would > be nice to have a tighter integration between Terracotta and > Tomcat, and > not having to rewrite the session manager in order to do it, as that > introduces the risk of bugs and could change tomcat's behavior. > With the > named classloaders, we can easily reference what classloader needs to > load the class on another node. > > What would be the next steps, I remember that the current tomcat > manager > likes to iterate through the entire HashMap for sessions, causing the > node to load all the sessions, this should be fairly straight forward > doing, by creating a lazy map, ie, when keySet or entrySet only > returns > the objects in actual memory > > thoughts on how to move forward? I'm sort of behind on Terracotta a > little bit, but I think I heard through the grapevine that there is an > API now? > > Filip > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
