A suggestion to how we can split this work:
Stian: Finish the UserSessionProvider (including mem, jpa and mongo implementations). Then
I can do the EntityManagerProvider and MongoConnectionProvider, then look at
transactions.
Bill: Split the remainder of the ModelProvider into RealmProvider and UserProvider, and at
the same time do the cache work.
Marek: Work on import/export to use same representations as admin endpoints.
----- Original Message -----
From: "Stian Thorgersen" <stian(a)redhat.com>
To: "Bill Burke" <bburke(a)redhat.com>
Cc: keycloak-dev(a)lists.jboss.org
Sent: Thursday, 10 July, 2014 8:19:16 AM
Subject: Re: [keycloak-dev] triple abstraction?
Ping me when you're online and we can have a Hangout to divide this work
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com>
> To: "Stian Thorgersen" <stian(a)redhat.com>
> Cc: keycloak-dev(a)lists.jboss.org
> Sent: Wednesday, 9 July, 2014 4:35:47 PM
> Subject: Re: [keycloak-dev] triple abstraction?
>
>
>
> On 7/9/2014 11:24 AM, Stian Thorgersen wrote:
> > I've reverted the JPA model provider, which is now the default in master.
> >
> > I also started a user session provider and changed the mem session
> > provider
> > from hybrid to implement this instead. Have a look at it at:
> >
> >
https://github.com/stianst/keycloak/tree/user-session-provider
> >
> > Specifically at:
> >
> >
https://github.com/stianst/keycloak/blob/user-session-provider/model/api/...
> >
> > How simple this was pretty much verifies to me that the approach I took
> > previously was utterly wrong!
> >
>
> Looks good so far. Let me know if I can help with anything as again,
> I"m kind of in a holding pattern.
>
> Bill
>
> --
> Bill Burke
> JBoss, a division of Red Hat
>
http://bill.burkecentral.com
>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev