I am far from being an Acegi expert, so take this FWIW.
Peter Kharchenko <[EMAIL PROTECTED]> writes:
> That's what I am currently doing. The ugliness comes in the first
> request, when the Context has not yet been placed into the session
> (since the filter does it at the end of the request proc
Joseph, Ben,
Joseph Dane wrote:
Ben Alex <[EMAIL PROTECTED]> writes:
Because the same thread is used for the duration of the HTTP request,
and the thread has security information removed from it at the end of
each request, there should not be any problem in a large web
application. You may
Ben Alex <[EMAIL PROTECTED]> writes:
> Because the same thread is used for the duration of the HTTP request,
> and the thread has security information removed from it at the end of
> each request, there should not be any problem in a large web
> application. You may like to confirm this yourself b
Peter Kharchenko wrote:
We're working on a large web application, which among other things,
relies on thread pools shared across multiple servlet sessions. This
appears to present a problem since the same thread may be used to
serve different users.
At the start of each HTTP request, HttpSes
Hi,
I am new to ACEGI, and have a basic question. ContextHolder, which
serves as a primary way of obtaining authentication state, is based on
ThreadLocal access.
We're working on a large web application, which among other things,
relies on thread pools shared across multiple servlet sessions. T
