If the component renders a URL to a secondary resource ( .js file, image file ) then the browser issues a seperate HTTP request (assuming no client side cache hit). The servlet container will assign a free thread to handle each request.
Dennis Byrne >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Thursday, October 26, 2006 10:24 AM >To: 'MyFaces Discussion' >Subject: Re: MyFaces and multithreading problem > >I'm not entirely sure about the threading model that MyFaces uses, however >I have noticed that callbacks from the extention filter may be on >different threads. > >Daniel > >> By definition, one request is only processed by one execution thread. I >> don't thins myfaces starts a new thread in order to do things (but in >> fact, >> I cannot confirm it). What I've found some times is a double submit issue >> (of course nothing to do with myfaces). >> >> Check that you are not submit the same form two times. >> >> Ricardo. >> >> >> On 26 Oct 2006 15:24:15 +0200, Irek Matysiewicz <[EMAIL PROTECTED]> wrote: >>> >>> We have a managed bean with session scope. It's used in one .jsp file. >>> Usually only one thread uses this bean, and everything works ok. But >>> today >>> we discovered, that two threads access the same getter method of the >>> bean at >>> the same time, and this leads to serious problems. Both getter >>> invocations >>> come from MyFaces. Of course the simplest method is to use >>> 'synchronized' >>> attribute with all methods visible to MyFaces, but this may slow down >>> our >>> application. >>> >>> Why does MyFaces use two threads here? Is there a better method than >>> synchronized? Maybe some setting in a configuration file? >>> >>> >>> ---------------------------------------------------------------------- >>> Jestes kierowca? To poczytaj! >>> http://link.interia.pl/f199e >>> >>> >> > > >
