I just drew up 2 proposals for CAS infrastructure:
https://www.lucidchart.com/documents/view?#4660-b97c-4f90267e-a851-1b180a60e9bc?branch=126766c7-1b44-42b5-a3d4-296f535c8c62
Yes, I can see from your ticketRegistry snippets that it's functionally equivalent, but I'd think you'd want an arrow on each CAS/memcached node pointing to itself as well as the other peer to indicate that each node communicates both with itself and peer.
(The particular node with which the memcached client communicates depends on the key and key hashing algorithm, which is a fairly vital configuration detail not exposed on the current MemCacheTicketRegistry component. We're planning to use the FNV1 hash, http://dustin.github.com/java-memcached-client/apidocs/net/spy/memcached/HashAlgorithm.html, for what it's worth. The primary consideration is that the hashing algorithm balances evenly across nodes for the given keyspace. FNV1 balances well from our testing and is more performant than the default implementation that simply delegates to String#hashCode().)
M -- 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
