Feature request: More backends

[ryanhellyer]

I normally prefer to disconnect my object cache backend from the static caching functionality, but this plugin is likely a convenient option for handling both one tool. What would make it even more convenient, is for it to automatically detect what caching backend (disk, Redis, Memcached etc) and use the corresponding one.

I assume a quick function check would be sufficient (and performant) to work this out on load.

This also adds some plugin bloat, but I think it would make the plugin more appealing to a broad range of users. Most people just use W3TC or WP Super Cache, but I'd like to be able to recommend something like WP Spider Cache if it could just be dumped in as a replacement.

[JJJ]

That makes sense, and I think like you mention it's not too difficult to achieve in an inexpensive way.

I spent some time last night making the object cache drop in engine-agnostic, with less documentation and direct mention to Memcache and Memcached. That's a first step. Next, is to actually code up the Redis drop-in, and fill in the functional gaps.

[ryanhellyer]

Cool. It was the "engine agnostic" comments which prompted me to suggest this actually.

[JJJ]

A year later, and I am still looking at and working on this. The Redis methods are different enough that it's taking some time to fill in the gaps, even using WP Redis & friends as a guide.