[wp-hackers] Caching as part of the core
lionel.pointet at globalis-ms.com
Fri Jul 20 14:22:55 UTC 2012
You say you can clear cache with each page saving, but when Otto says
"page cache", it means a whole HTML page, generated with one post (as
you mean) and with some other components like nav-menus, sidebars and
widgets which can access to other contents stored in DB.
So you cannot just think a web page is one post: you said it yourself,
developers bring some rich components.
Indeed, since it's the developers which bring those components, why
aren't they considering their cache? Why is it the core's
responsibility? It just won't work.
And why aren't you happy with the Object Cache API? It is pretty simple,
useful enough and the default saving (an array in a class) is actually
good to maintain the number of queries as low as possible on each page
with a default installation. But if you want, WordPress let you add a
persistant system over that API (see the object-cache.php drop-in and
the multiple classes available on the web): you just have to provide
your class interfacing with that system, and it's already working thanks
to the API calls done all over the core...
I think choices made are good enough to let user run WP on a lot of
hosting services, let developers take care of their own caching systems
easily and keep WordPress as light as possible.
Speaking about 3rp party optimizations like minifying and stuff, WP core
could take some responsibilities here but I don't think this is a top
priority since there are plugins doing it already and it's much about
comfort, not functionality.
Le 20/07/2012 15:10, Almog Baku a écrit :
> 1. First of all, great replay
> 2. I am really not agree with you. The common user NEED caching. you may
> started out from the assumption that the most users using near-by hosting..
> today, the internet is so global that many israeli users for example, host
> ther website over dreamhost.. or maybe US client browse to israeli website..
> Also, google detect this website as slow..
> 3. You can cache pages and keep the website update by db.. (by removing
> page cache every saving)
> 4. With the default installation, wordpress is really tiny and small.
> But today, a lot of programers develop over WP website who are basicly
> simple but have a lot of components and actually rich(sliders, multiple
> post-type etc).. I think we should consider it.
> 5. Maybe if the core will recognize the common mem-caching system and
> try to connect to them automatically(with option do disable of course) it
> will be awesome.
> 1. You offer here a great idea!
> 2. I think we should at least develop api(with basic implementation)
> that the 3rd-party plugins can extend and improve.
> 3. If there will be some api-interface, and we will encourage for it in
> the plugin repository it will serve us well.
> 1. By my opinion the current system isn't good enough.
> 2. Actually the current ststem is joke. it only save some vars in global
> array.. mean nothing.
> *I think that minify and browser caching at least are the minumum.* what do
> you think guys?
> ~ Almog
> On Fri, Jul 20, 2012 at 3:41 PM, scribu <mail at scribu.net> wrote:
>> On Fri, Jul 20, 2012 at 2:01 AM, Mike Schinkel <mike at newclarity.net>
>>> So in summary, I would love to see WordPress implement standard caching
>>> *APIs* in core that would enable more people to fine tune their caching
>>> so 3rd party caching plugins could be easier to install and be made more
>> WordPress already has a standard object caching API: wp_cache_set(),
>> wp_cache_get(), wp_cache_delete(). It is used extensively througout Core
>> and there already are several 3rd party caching plugins that implement that
>> If you meant a standard _page_ caching API, you should have said so.
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers