My impression was Thread Local gives you an instance of an Object for each thread. If you run Tomcat with 100 thread pool you will have at most 100 different objects no matter how many connections you have and since a new connection is handled by an existing thread it will pick up the values from the previous request that used that thread. I think you could use the request to store the value in but as I said I don't think it's necessary. I'll post a request on the Dev list. It would be nice to solve this problem because it seems all the parameters I'd like to have control over are the ones with default values.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org