> Don't fall into the trap of premature optimization! Hm. Maybe I'm in this trap already. But what is wrong with binding a resource directly to the request when it is used exactly for the lifetime of the request? For me this only sounds logical compared to the pragmatic approach using a ThreadLocal object. Are there any technical reasons against storing in the request?
Regards, Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
