Shibboleth Developers

["Scott Cantor" <>]

> And item that I thought about, be rejected, was:
> - Making the attribute resolution process multi-threaded.  I rejected
> this because it would add a significant amount of complexity to the
> process and make it harder to track exactly what is going on.  In
> addition the Servlet container is already allocating at least one thread
> per-request. Additional pools of threads could result in resource
> starvation or unexpected interaction with the container.

I assume by this you meant parallelizing individual executions of the
resolver for a request by running connectors in parallel? It's not
single-threaded across requests now, right?

I agree, that's a lot of effort and risk for little gain, particularly with
caching supported anyway.

-- Scott