I don't know how many of the CAS developers have looked at the CAS Client code recently. One of the things I'm thinking about though is whether we need a ProxyDecider interface (right now all Proxy decisions happen in the Proxy20TicketValidator and either you supply a list of proxy chains or say "accept any chain").
Obviously, the cleaner way is to introduce an interface with two implementations (one that accepts a chain and one that says yes to anything). The simpler way is to keep the implementations in the TicketValidator. Can anyone think of other possible implementations that would help justify the added complexity of moving that out to an interface? -Scott -- Scott Battaglia Application Developer, Architecture & Engineering Team Enterprise Systems and Services, Rutgers University v: 732.445.0097 | f: 732.445.5493 | [EMAIL PROTECTED] _______________________________________________ cas-dev mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas-dev
