Hi, thanks for your input. It’s likely that additional opcode caches will be supported after version 1.0. I will likely add plugin (add-on) support so that 3rd parties can add submit their own additions to the framework. In any case, the more requests I receive the faster I can prioritize the feature.
Thread Starter
Ovidiu
(@ovidiu)
great.
its not as if eaccelerator is better than the others, but I’d have to remove eaccelerator, install APC, which is quite a hassle when you’re hosting a couple of sites, relying on eaccelerator already…
@fredericktownes
one more vote from my side feature request for eaccelerator
I took a little time to put this together since I use eAccelerator (WP Super Cache Plus) and I wanted to try out W3TC. It’s only lightly tested and you’ll have to apply the patch yourself, but it seems to work. 🙂
http://datenschwanz.net/2009/12/10/w3-total-cache-eaccelerator/
It’s on the roadmap for the next release. Thanks though.
will it be included in 0.9 ?
Could we get support for ordering minified files please?
Could we get the option to select specific users that don’t get zipped pages instead of an all or nothing choice?
Could we get support for ordering minified files please?
Files are currently combined in order. So you want some sort of drag and drop to cure dependencies? This is already in the roadmap.
Could we get the option to select specific users that don’t get zipped pages instead of an all or nothing choice?
If a user agent doesn’t support compression, they don’t receive it. That’s the industry standard paradigm. Targeting specific users requires IP addresses, so that feature won’t be added. If you mean sending uncompressed files to specific user agents, again because compression support is automatically detected, I don’t see the benefit of this case.
fredericktownes,
And accelerator support? cgs2 fix won´t apply to 2.8.5.1
dbasulto:
Do you want the patch updated for 2.8.5.1?
