On Thu, Mar 5, 2009 at 6:53 PM, Brian Akins <[email protected]> wrote: > Is this based on the existing mod_memcache?
No. It is based on mod_dbd. New one (http://www.mail-archive.com/[email protected]/msg42922.html) to be precise. mod_memcache, if we are talking about http://code.google.com/p/modmemcache/, is too simple. I need multiple name pools to multiple servers. Something like <MemcachePool "name1"> Server 192.168.0.1:11211 Server 192.168.0.2:11211 Server 192.168.0.3:11211 Server 192.168.0.4:11211 Server 192.168.0.5:11211 Other options... </MemcachePool> <MemcachePool "name2"> Server 192.168.0.6:11211 Server 192.168.0.7:11211 Server 192.168.0.8:11211 Server 192.168.0.9:11211 Server 192.168.0.10:11211 Other options... </MemcachePool> Also I will implement hook in module. Hooked function can filter servers list. For example (in python pseudo code): def dead_or_alive(servers_list): new_list = [] for server in servers_list: if server is in some list in shared memory, it is alive and it is not overloaded then: new_list.add(server) return new_list If returned list differs from saved one, than we recreate connections (maybe something smarter). This feature enables us to create dynamic, not static servers list. For high availability clusters for example. Alright, i will ty to base it on apr_memcache then. -- Marko Kevac
