[TYPO3-project-4-3] memcached

[Dmitry Dulepov]

Hi!

Steffen Kamper wrote:
> while testing memcached on one server i saw, that there is no warning if
> memcached isn't installed. As you don't see it you may think all is
> running fine, but cache is misconfigured.
> 
> I think the best would be a warning and a fallback to default cache (I
> didn't inspect what happen with this configuration).
> 
> What do you think?

I think the person who installs the system, should know what (s)he is doing... If (s)he does not understand what (s)he is doing, (s)he should not do it at all but hire a professional.

Recovering from errors is good but to a certain limit I think. In case of caches I would prefer to abort  because it is a real failure on the server. For example, if memcached dies, falling back to the default cache can be very undesireable. Producing error 500 would attract admin's attention much faster.

I can be wrong, of course. There are different use cases.

-- 
Dmitry Dulepov
In TYPO3 blog: http://dmitry-dulepov.com/article/typo3-seo-keywords-from-the-typoscript-and-a-page.html
LinkedIn: http://www.linkedin.com/in/dmitrydulepov
Twitter: http://twitter.com/dmitryd
Skype: liels_bugs