[keycloak-dev] [async] Why is async jaxrs being used?
Pedro Igor Silva
psilva at redhat.com
Sat Apr 1 14:22:42 EDT 2017
Btw, the main design around the AuthZ API was provide a async and
non-blocking API for policy evaluation.
On Sat, Apr 1, 2017 at 12:15 PM, Bill Burke <bburke at redhat.com> wrote:
> I don't understand why async-http support for JAXRS is being used for
> Authz requests. Async HTTP is only useful when you want to limit the
> amount of long running requests or you have an operation that may block
> for some time. Do you want to limit the number of authz requests that
> can happen at one time? Or, do you have an operation that may block?
> Otherwise I don't see the point of using async HTTP. It complicates the
> Looking at your ScheduledPermissionEvaluator you aren't even using the
> Executor that is passed into the constructor so its all happening in the
> same thread anyways.
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
More information about the keycloak-dev