Shibboleth Developers

But how can we be sure that the same thread that processes the HS request 
from the browser will be the same that processes the AA request from the SP 
to the IdP?


From: Chad La Joie < 
>
It's not directly stated that there must be one-to-one relationship between 
requests and threads but it's strongly implied (for example, the spec says 
that the request and response objects have to be scoped to one thread for the 
duration of the request). I'm sure some one could come up with an inventive 
way to get around this but I've never seen any container try it. The thread 
local method has worked in all the containers I've used (Tomcat, JBoss, 
Webspehere, Weblogic, Resin, Jetty)

Walter Hoehn wrote:

    Agreed, although this is relying on unspecified behavior. I can't imagine 
why any container would use a different thread for the filter and the 
servlet, though.

    -Walter


    On Oct 3, 2006, at 5:22 AM, Chad La Joie wrote:

        Hey Ulrich,
        Probably the most straight-forward way would be the bind the 
attributes to thread-local variables within the filter then write a custom 
data connector, for the attribute resolver, to pull the information from the 
thread. That way you won't have to customize the IdP code, you can just use 
the normal IdP extension mechanism.