On Fri, Mar 9, 2012 at 1:09 PM, Marvin Addison <marvin.addi...@gmail.com> wrote: > Serialization matters in ways that are well documented.
[snip] > For the short term I would like to offer my work on > MemcachedTicketRegistry [5] for consideration to be included in the > 3.5 release. I'm a +1 as long as it fits into the release strategy, and doesn't substantially delay the 3/20 RC1 target. > While appearing in the next release would make it easier > for us to use in the Spring/Summer timeframe, I'm quite certain it has > value generally for memcached deployers. In any case we plan to use > this code for our next production release at Virginia Tech. Curious if you've considered RMI replicated Ehcache as well. Folks are having a lot of success with this approach, and the deployment is very straight forward. So much so that I've thought that the default ticket registry could be Ehcache even for a single node deployment. Then to go multi-node you just add the RMI endpoints in the Ehcache config. Best, Bill > > M > > [1] > http://dustin.github.com/java-memcached-client/apidocs/net/spy/memcached/transcoders/SerializingTranscoder.html > [2] http://code.google.com/p/kryo/ > [3] > https://wiki.jasig.org/download/attachments/26510787/cas-stress-registry-dev.jmx?version=1&modificationDate=1329934450042 > [4] https://gist.github.com/2007751 > [5] https://github.com/serac/cas/tree/memcached-ng > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: wgt...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
