[security-dev] Caching Interfaces
Anil Saldhana
Anil.Saldhana at redhat.com
Tue May 14 11:41:02 EDT 2013
On 05/14/2013 10:22 AM, Pedro Igor Silva wrote:
> It looks good for me. Not sure if we should spend much effort writing a in-house cache mechanism.
The default cache is just an in-memory subclass of the concurrenthashmap.
>
> You PR, if I got it right, is basically an abstraction API for any cache mechanism (ispn, terracota, coeherence, etc).
If you see the separate thread on PL-integration projects, I am guessing
that the various cache integration will go into the plintegration github
organization.
>
> ----- Original Message -----
> From: "Anil Saldhana" <Anil.Saldhana at redhat.com>
> To: security-dev at lists.jboss.org
> Sent: Tuesday, May 14, 2013 10:42:13 AM
> Subject: [security-dev] Caching Interfaces
>
> Shane/Pedro,
> friday, I put in a PR for a caching interface (api/impl) that will
> allow external integration to various caching frameworks. This feature
> is a gap we have. We did broach caching few weeks back.
>
> https://github.com/picketlink/picketlink/pull/107
>
> We can modify the PR based on your feedback.
>
> Regards,
> Anil
> _______________________________________________
> security-dev mailing list
> security-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/security-dev
> _______________________________________________
> security-dev mailing list
> security-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/security-dev
More information about the security-dev
mailing list