Raise your hand if you've miscounted zeros in configuring a timeout… <raises hand>
I too think improving the experience of configuring a CAS deployment is a modest but important contribution. Existing deployers will touch their configuration on the upgrade to CAS 3.5, not least to get to the new TicketGrantingTicketExpirationPolicy with the feature of preventing TGTs from being renewed forever. At that point, people are touching this configuration anyway, and will benefit from the time units involved being clearer. Andrew On Mar 13, 2012, at 10:35 PM, William G. Thompson, Jr. wrote: > On Tue, Mar 13, 2012 at 10:00 PM, Scott Battaglia > <[email protected]> wrote: >> As I mentioned in the pull request (and especially since I advocated that >> constructor :-D), I like the constructor method. However, I don't feel >> there's enough compelling change to (a) remove existing constructors and (b) >> change all of the default configuration for a 3.5 release. > > Then you haven't done enough CAS deployments! > >> >> That just seems like making a change for the sake of making a change, not >> for the benefit of existing users. > > Not at all. Improving the experience of configuring a CAS deployment > is a modest but important contribution. > > Best, > Bill > > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
