<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 30/03/16 15:43, Bill Burke wrote:<br>
</div>
<blockquote cite="mid:56FBD7FD.60203@redhat.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
JAX-RS async can be enabled per resource, so its really up to you
to decide if Authz needs it. <br>
<br>
Async doesn't make sense for core KC autthentication. KC Identity
broker does not wait/block for a response on a login.
Authenticators are not waiting/blocking for responses either.
Waiting/blocking only happens on backchannel logouts and
background admin operations.</blockquote>
Not directly related to JAX-RS Async, but IMO at least the
performance of backchannel logout in ResourceAdminMAnager can be
slightly improved if we send the backchannel logout requests
asynchronously. Currently if you are logged to 5 apps, you first
need to send backchannel logout to product-portal, then wait for
response, then send another backchannel logout to customer-portal,
wait again etc. IMO sending 5 requests asynchronously can improve
performance of logout and it can be done quite easily inside
ResourceAdminManager.<br>
<br>
Marek<br>
<blockquote cite="mid:56FBD7FD.60203@redhat.com" type="cite">
Somebody is going to have to show me real tangible benefits before
we switch core KC to use Async JAX-RS or some async event driven
SPI, because right now, with our currently functionality and our
roadmap, there is no need for an async model.<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 3/29/2016 9:57 PM, Raghuram
Prabhala wrote:<br>
</div>
<blockquote
cite="mid:597548124.123268.1459303053944.JavaMail.yahoo@mail.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff;
font-family:Courier New, courier, monaco, monospace,
sans-serif;font-size:13px">
<div id="yui_3_16_0_ym18_1_1459302142803_4062" dir="ltr"><span
id="yui_3_16_0_ym18_1_1459302142803_4061">+1. Makes sense
for even KC (as Identity broker waiting for a response
from Identity provider or as Identity provider waiting for
a response from Authenticators)</span></div>
<div class="qtdSeparateBR"
id="yui_3_16_0_ym18_1_1459302142803_4060"><br>
<br>
</div>
<div class="yahoo_quoted"
id="yui_3_16_0_ym18_1_1459302142803_3969" style="display:
block;">
<div style="font-family: Courier New, courier, monaco,
monospace, sans-serif; font-size: 13px;"
id="yui_3_16_0_ym18_1_1459302142803_3968">
<div style="font-family: HelveticaNeue, Helvetica Neue,
Helvetica, Arial, Lucida Grande, sans-serif; font-size:
16px;" id="yui_3_16_0_ym18_1_1459302142803_3967">
<div dir="ltr" id="yui_3_16_0_ym18_1_1459302142803_3966">
<font id="yui_3_16_0_ym18_1_1459302142803_3965"
face="Arial" size="2">
<hr size="1"> <b><span style="font-weight:bold;">From:</span></b>
Pedro Igor Silva <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:psilva@redhat.com"><psilva@redhat.com></a><br>
<b><span style="font-weight: bold;">To:</span></b>
keycloak-dev <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:keycloak-dev@lists.jboss.org"><keycloak-dev@lists.jboss.org></a>
<br>
<b><span style="font-weight: bold;">Sent:</span></b>
Tuesday, March 29, 2016 9:47 PM<br>
<b><span style="font-weight: bold;">Subject:</span></b>
[keycloak-dev] Async HTTP Request Processing<br>
</font> </div>
<div class="y_msg_container"
id="yui_3_16_0_ym18_1_1459302142803_4176"><br>
Hi,<br>
<br>
I'm working with the AuthZ Java API in order to
make it more event-driven and non-blocking. During our
F2F, I've discussed some very interesting requirements
with Marc Savy around that.<br>
<br>
I would like to know if makes sense to enable
JAX-RS Async support to some AuthZ REST endpoints,
which are basically using this API to evaluate
policies using different providers (where these
providers can be executed in parallel).<br>
<br>
Regards.<br>
Pedro Igor<br>
_______________________________________________<br>
keycloak-dev mailing list<br>
<a moz-do-not-send="true"
ymailto="mailto:keycloak-dev@lists.jboss.org"
href="mailto:keycloak-dev@lists.jboss.org"
id="yui_3_16_0_ym18_1_1459302142803_4177">keycloak-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/keycloak-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
keycloak-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bill Burke
JBoss, a division of Red Hat
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://bill.burkecentral.com">http://bill.burkecentral.com</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
keycloak-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a></pre>
</blockquote>
<br>
</body>
</html>