[Tickets #2781] Enhancements for memcache session driver

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2781
-----------------------------------------------------------------------
 Ticket             | 2781
 Updated By         | kevin_myer at iu13.org
 Summary            | Enhancements for memcache session driver
 Queue              | Horde Framework Packages
 Version            | HEAD
 State              | Feedback
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | 
+New Attachment     | memcached.php.patch
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-10-17 12:39) wrote:

> Looks much better, but I still have two suggestions:
> - the operators in _getConForId() need some more horizontel whitespace

Sorry missed that.  It might be helpful if the CODING_STANDARDS webpage had
a fixed font specified, as it's somewhat difficult to pickup the spacing
from there.  I know I could look the same doc up in a terminal window but a
Courier font would help the webpage.

> - I personally would prefer to use the functional interface to the 
> memcached extension. The OO interface doesn't gain us anything here 
> is probably not available in older versions of the extension.

I'll change it.  I had used  pure OO code $foo=$bar->getConId($id)->get($id)
but that didn't work under PHP 4, so I had partially backed it out but its
not much of a difference to use the functional interface, and maybe easier
to read.

I think this will be the extent of how far this particular session handler,
using the PECL memcache extension can really go.  With libmemcache and the
php-mcache, more robust configurations with easier failover are possible,
but since the base PECL memcache functions don't support multiple servers, I
think a different driver based on a different memcache library would be
better.  The downside to that is an additional dependency but anyone who
needs that kind of reliability has probably already worked out something
in-house anyway.  But it would be nice to get something into public code, so
us smaller players don't have as much to maintain locally.

Summary of enhancements over original driver:
Ability to specify more than one server (but no automatic failover of data
for downed servers)
Ability to specify persistent connections
Ability to specify compression of data