Change History (3)
#2
@
13 years ago
- Milestone Awaiting Review
- Resolution → wontfix
- Status new → closed
Rather than trying to implement interfaces to every caching engine under the sun, WordPress instead provides the means for plugins to provide these interfaces.
Alex Mills wrote an article on this a few years ago.
TL;DR: Persistent caching isn’t needed for most sites and is a pain to get working in all hosting environments. Instead WordPress makes it really easy to install a caching plugin if you need it.
There are many plugins in the plugin directory that add support for APC, Memcached, Xcache, static page caching...
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I do think we have a complete system except it's missing the actual code to use external caching. Personally I'm fine with how it is right now since I don't use memcached or APC. I use a APCu what is a variant of APC.
So I don't think something like this can be added to core since things will change. There is now memcache and memcached for example and I'm pretty sure that APC will fade away for something like APCu.