On Mon, 2010-11-08 at 15:46 +0000, Mark Thomas wrote: > I did consider that approach but rejected it for a couple of reasons: > - Mapper needs to be manager aware - it isn't currently
Add a one method interface to be able to perform a session lookup. > - Performance Likely, having to do String manipulation/parsing is much worse than a map lookup. > Now the clean-up is in place and we can focus on the actual changes I'll > probably go back and take another look at this option. It is almost > certain I didn't fully explore all the possible ways of doing this. > > > I don't agree with adding a version number/id to the session id, or > > changing its format, this will create legacy issues, as we can see right > > now. > > An understandable concern. I'll up that to -1, with another concern I've just thought about: if using a session id path which includes more than one webapp, the version numbers will have problems matching between the two webapps. Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
