When using something like repcached you can reconfigure the web flow storage to use request storage instead of session storage without any issues. That's what we do at Rutgers.
Sent from my Verizon Wireless BlackBerry -----Original Message----- From: Johan Reinalda <[email protected]> Date: Mon, 06 Apr 2009 16:59:26 To: <[email protected]> Subject: [cas-user] CAS session replication All, in the case of an Active/Standby clustered CAS setup (with repcache), does it really matter whether you have (web) session replication ? ie. If we don't care about a user having re-submit in the very small possibility of them hitting submit during a failover scenario, can we simply *not* do session replication (and thus ignore the Tomcap session replication or Springs session capabilities documented; both of which we have tested and work fine, by the way.) Are we missing something here ? Thanks, Johan -- 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-user -- 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-user
