Session support

> 1. Why are separate servers required?

This is outdated documentation if you are using the 6.x-1.5 or later release. You no longer need to keep user and session data in a separate memcache instance. This was required before we had wildcard support in the module (first added in 6.x-1.5). At this time, the main reason you may want to split out a given table (be it user/session data or another) is because the data is more important to you than other data (ie user/session data which isn't really a cache) and you want to ensure that nothing else can cause your data to be evicted. Memcached evicts objects with an LRU (least recently used) algorithm so inherently helps minimize this as well.

Leaving this issue open, as the documentation needs to be updated.

So, I can just add this line and that's it?

$conf = array(
// The path to wherever memcache.inc is. The easiest is to simply point it
// to the copy in your module's directory.
'cache_inc' => './sites/all/modules/authcache/authcache.inc',
'session_inc' => './sites/all/modules/memcache/memcache-session.inc',
'memcache_servers' => array('localhost:11211' => 'default'),
'memcache_key_prefix' => 'madf_',
);

No need to setup another server with different port?

Thanks

Yes, that config looks like it should work. In fact, memcache_servers will default to localhost:11211, so you don't even need to define that if you don't want to.

Taking this ticket as part of my documentation efforts.

Drupal 6 has not been supported for a long time.