> But you need a production team to install Memcached instances, you need > supervision > team to watch Memcached processes... More configuration, more processes > involved, > more network routes to open in firewalls, more bandwith consumed... more > probabilities to have problems...
Ok, you've made a valid point. The proposed design violates the principal of simplicity for HA services. > Why not choose the easiest solution in terms of architecture : > send HTTP logout calls from client side (logout page) ? Because it requires configuration data that is a management burden over time. I can say this with authority because we did it formerly and it's a drag. I really think the back channel solution is cleaner conceptually, but I can admit that when you throw enterprise architecture and HA into the mix it gets complicated. If you could propose a means to do front channel logout without the need for per-service metadata, I could get on board with the proposal. 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-dev
