[cas-dev] JBossTicketRegistry

[Scott Battaglia]

Jen,

Based on your thoughts here (and yes I know I'm a little behind in replying
;-)), I plan on making some changes to the JBossTCacheTicketRegistry.  I've
created a JIRA issue for it.

-Scott


On 10/25/06, Jennifer Yang <jyoonyang at gmail.com> wrote:
>
> Hi Scott,
>
> It's me again.  :-)
>
> Hey, we want to port JBossCacheTicketRegistry for CAS 3.0.  While in
> the process, I was doing slight refactoring and wanted to hear your
> opinion.
>
> 1. Change the constructor of Proxied*Ticket to take
> JBossCacheTicketRegistry instead of TreeCache
> 2. Pulled out the inner classes to be on their own
> 3. Added
>    public void updateRegistry(Ticket ticket) {
>        ...
>        this.cache.put(JBossCacheTicketRegistry.FQN_TICKET,
> ticket.getId(), ticket);
>        // might try to distribute the ticket across different nodes to
> minimize replication payload
>        ...
>    }
> 4. Any Ticket methods that changes Ticket state calls
> updateRegistry(), instead of calling cache.put() directly
>
> Do you see any issues with this?
>
> Thanks again!
> --Jennifer
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20061204/aa2aa01c/attachment.html