<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I've created a JIRA issue to track this
work:<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://issues.jboss.org/browse/PLINK-202">https://issues.jboss.org/browse/PLINK-202</a><br>
<br>
On 20/06/13 00:22, Pete Muir wrote:<br>
</div>
<blockquote
cite="mid:72075DCA-FA7E-48EC-8AA3-01F1043192EB@redhat.com"
type="cite">
<pre wrap="">Shane and I spent time working through this earlier today. We think we can move all IDM APIs to stateless access, passing in the lightweight SecurityContext object to calls.
Shane is going to work on it this week I think.
On 13 Jun 2013, at 17:16, Jason Greene <a class="moz-txt-link-rfc2396E" href="mailto:jason.greene@redhat.com"><jason.greene@redhat.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">The IDM apis should be designed to support stateless access and not require any form of synchronization, volatiles, or CAS. It's fine however to have caching plugins which do keep state and are designed for concurrent access. However, those should be implemented using near-lockless strategies. I can help with that if you need it.
On Jun 13, 2013, at 8:15 AM, Shane Bryzak <a class="moz-txt-link-rfc2396E" href="mailto:sbryzak@redhat.com"><sbryzak@redhat.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Do you mean DefaultStoreFactory.createIdentityStore() ? I actually
don't think we should be caching the stores here at all, I'll create a
JIRA to investigate this.
On 13/06/13 22:27, Bill Burke wrote:
</pre>
<blockquote type="cite">
<pre wrap="">IdentityManagerFactory's fields are all HashMaps and you're populating
the store cache on the fly. Is there any reason you don't
pre-initialize the store cache?
On 6/12/2013 6:22 PM, Shane Bryzak wrote:
</pre>
<blockquote type="cite">
<pre wrap="">IdentityManagerFactory is designed to be application-scoped (or even
container scoped), while IdentityManager is a lightweight object that is
designed to be request-scoped (as each IdentityManager has its own
SecurityContext with potential references to short-lived objects, such
as entity managers). Which concurrency issues have you found? We
should raise issues in JIRA to address these before we hit final.
On 13/06/13 07:26, Bill Burke wrote:
</pre>
<blockquote type="cite">
<pre wrap="">How should concurrent access to IDM storage be handled? Right now I see
a lot of concurrency issues in the code that will pretty much force you
to create an IdentityManagerFactory and IdentityManager per request.
</pre>
</blockquote>
<pre wrap="">_______________________________________________
security-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:security-dev@lists.jboss.org">security-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/security-dev">https://lists.jboss.org/mailman/listinfo/security-dev</a>
</pre>
</blockquote>
</blockquote>
<pre wrap="">
_______________________________________________
security-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:security-dev@lists.jboss.org">security-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/security-dev">https://lists.jboss.org/mailman/listinfo/security-dev</a>
</pre>
</blockquote>
<pre wrap="">
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
security-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:security-dev@lists.jboss.org">security-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/security-dev">https://lists.jboss.org/mailman/listinfo/security-dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>