Josh Berry wrote > On Thu, Jan 16, 2014 at 5:14 PM, gcollins < > gareth.o.collins@
> >wrote: > >> Hello Les, >> >> Thankyou very much for the answer! >> >> Yes I could do that but it doesn't really solve my problem. When requests >> for authentication spike, I would either need to allocate a large number >> of >> threads for the ExecutorService thread pool...or slow down authentication >> for users by queueing the requests up (the authentication request could >> take >> several seconds to complete). >> > > I'm curious on how this wouldn't be the case for any asynchronous > approach. The underlying custom authentication mechanism itself is asynchronous. Only trying to keep to existing Shiro interfaces would force me to hold threads. thanks, Gareth -- View this message in context: http://shiro-user.582556.n2.nabble.com/Asynchronous-Authentication-tp7579507p7579536.html Sent from the Shiro User mailing list archive at Nabble.com.
