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(a)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
code.
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.
Bill
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev