[TYPO3-core] FYI72: enhancements to memcached caching backend

[Dmitry Dulepov]

Hi!

Karsten Dambekalns wrote:
> addServer() accepts unix sockets the same way as connect(), so those can
> be combined. It makes sense to look at what happens when a server is not
> available, given the fact that an error is counter-productive to
> failover. ;)

Here I have 10 second delay in get/set methods and finally a huge error message on the screen with paths to current site and lots of technical info if server is unavailable.

When using addServer, connections problems do not happen until someone calls get() or set() or any other function. So exception catching does not work. When those get/set/other are called, it is too late to catch errors already (page processing is in progress!). So I would prefer to connect to servers first and ensure that they are available. It is more effective than the current approach.

About the pool. Using memcached makes sense when it is local. Network delays will kill any benefits of using memcached. Having more than one local memcached is possible and there is no real problem connecting to more than one instance as it is extremely fast.

Your opinion? :)

-- 
Dmitry Dulepov
TYPO3 core team
In the blog: http://typo3bloke.net/post-details/zend_debugger_goes_64_bit_on_mac_os_x/
My TYPO3 book: http://www.packtpub.com/typo3-extension-development/book