note 87378 rejected from memcache.ini by danbrown

Note Submitter: e dot borger at grib dot nl ---- The current memcache 3.0.2 (beta) has options for server redundancy. Has anyone tried this yet? Although it's beta, it would suit our client's needs perfectly as a session handler and it would reduce the need for us to rewrite large sections of code and reinvent the wheel. Documentation on these new features is very hard to find unfortunately. What I've come up with in a situation with two memcached servers and 6 webservers and with the following demands: 1) users keep their sessions when a webserver fails or loadbalancing decides to move them to another server 2) users keep their sessions when a memcached server fails (and 3) it needs to be fast) session.save_handler='memcache'; session.save_path='tcp://host1:11211, tcp://host2:11211'; memcache.redundancy=2; memcache.session_redundancy=2; memcache.allow_failover=2; Would that work? (I've tried explaining memcached is not directly meant for this job and that it should actually be run on the webservers - they see it as just a very fast database)