[cas-dev] JBossTicketRegistry

[Scott Battaglia]

Jennifer,

We wrap the tickets in a proxy so that when the iternal state of a ticket is
modified, we can propogate those changes across the network (which is why
you'll see a few methods doing a "put").  isValidFor updates an internal
counter and "last use" time that are used when determing the expiration
policy.

The JBossTicketRegistry may require 3.0.5.  I'm not 100% sure off the top of
my head.
-Scott

On 9/21/06, Jennifer Yang <jyoonyang at gmail.com> wrote:
>
> Hi Scott,
>
> I am working on clustering CAS servers under JBoss.  I downloaded
> JBossTicketRegistry implementation, and have some questions.
>
> What is the reason for creating proxy tickets?  I noticed you are warpping
> TreeCache in the proxy tickets.  How is that to be used?
>
> For ProxiedServiceTicket, it seems like all the methods are pretty much
> delegating to the passed in ticket, except for isValidFor().  I don't
> understand why the ticket is added to cache again, regardless of the result
> of isValidFor.  Does isValidFor() change the state of the Ticket or
> something, therefore you have to update the cache?
>
> Also, what version of CAS server is this written for?  I am seeing some
> compilation error due to missing methods.  I have CAS server 3.0.4
>
> Thanks always for your help.
> --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/20060922/8b36123b/attachment.html