[keycloak-dev] KeycloakSession question

[Bill Burke]

KeycloakSession is analogous to an EntityManager in JPA.  It only exists 
for the duration of the request.  What you'd want is for File-based 
storage to queue up writes and flush them when the KeycloakSession is 
committed.

On 4/10/2015 9:15 AM, Stan Silvert wrote:
> Is KeycloakSession always short-lived?
>
> If so, it might be relatively easy to make the JSON File based
> persistence more robust and probably fix the cache tests that currently
> fail with it.
>
> All KeycloakSessions would share the same in-memory model.  When a
> KeycloakSession ends and requests to write the model to disk, all new
> requests for access to the model are blocked.  When all active
> KeycloakSessions are done, we write out the model and unblock the new
> KeycloakSessions.
>
> But this only works if we can assume KeycloakSession is short-lived.
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com