[keycloak-dev] abstracting out picketlink

[Bill Burke]

Picketlink has gotten even more generic/abstract with the latest 
release.  Every single API (User, Role, etc.) is now optional.  Its more 
a federated JDO store than a IDM store now.  Having dived into the code, 
I'm a little worried how its going to perform.

On 7/31/2013 4:49 AM, Stian Thorgersen wrote:
> Just a little smile ;)
>
> I think this is better in any case. IMO the IDM interfaces are to generic/abstract to be consumed directly + they do change the API to frequently.
>
> ----- Original Message -----
>> From: "Bill Burke" <bburke at redhat.com>
>> To: keycloak-dev at lists.jboss.org
>> Sent: Wednesday, 31 July, 2013 2:47:54 AM
>> Subject: [keycloak-dev] abstracting out picketlink
>>
>> Don't laugh, I know I said I wasn't going to do this, but I am now.
>> Abstracting out picketlink will make an easier transition for me to fit
>> in the new version of Picketlink.  Obviously it will also allow us to
>> dump Picketlink too if it turns out its just not going to scale or they
>> aren't accepting our pull requests.  Hopefully we won't have to do that
>> though.
>>
>> So merge from master often as I'll be committing as I go.
>>
>> --
>> Bill Burke
>> JBoss, a division of Red Hat
>> http://bill.burkecentral.com
>> _______________________________________________
>> 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