If you're willing to go outside of Java, have a look at RubyCAS-Server (http://code.google.com/p/rubycas-server). It shouldn't be too hard to set this up for fault-torrent clustering by using a combination of mongrel_cluster with Apache or Pound reverse-proxy.
Nathan Schimke wrote: > I've read through the list archives, and I've found some tantalizing > hints but no clear answer to this: > > If I'm looking for a fault-tolerant CAS service for a multi-tier > application (fault-tolerant in the sense that a server can "disappear" > and the end users aren't affected), am I really stuck with rolling my > own implementation or waiting for the CAS 3.1 release? > > Or has somebody got an implementation which works in production and > they'd be willing to share, even if they can't actively support it? > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas This e-mail message is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited. Le contenu du pr'esent courriel est privil'egi'e, confidentiel et soumis `a des droits d'auteur. Il est interdit de l'utiliser ou de le divulguer sans autorisation. _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
