You could do something like that, or you could just have the servlet pass that into the supporting code/beans. It'd be a lot cleaner and clearer design wise to just pass the information, either encapsulated into a new object or just the values you need.
--mikej -=------ mike jackson [EMAIL PROTECTED] > -----Original Message----- > From: Roggeveen, Brian P [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 31, 2003 3:53 PM > To: '[EMAIL PROTECTED]' > Subject: Threading Question > > Hello, > > I was wondering if it is safe to assume that when using the multithreaded > model, a single unique thread will handle each incoming request? In other > words, does the servlet container implement a thread per connection model > or > is there a way to specify this configuration? > > The reason I ask is that at any given point within my servlets' supporting > code/beans, I would like to have access to the HttpSession instance that > corresponds to the client for whom the current line of code is being > executed. Another way of looking at the situation would be at any given > point within my servlets' supporting code/beans, I would like to have > access > to the HttpRequest that caused this particular line of code to be executed. > In order to accomplish this, I envisioned using a Map that contained > thread > keys and HttpSession values. As requests came in, the Map would be updated > appropriately such that supporting code need only look up an HttpSession > using the current thread. Maybe I'm making this more complex than it needs > to be. > > Thanks! > Brian Roggeveen > EDS - Work Force Management > Voice: (314) 264-8991 > Fax: (314) 264-8901 > Email: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
