[wp-hackers] Caching as part of the core

[Brian Layman]

In the end, it may be semantics because while Fragment Cache doesn't 
happen automatically, as does everything I consider object caching,  it 
would most likely use the same get and set methods. I think most of the 
items on Mike's list are actually fragment caching examples*, but the 
object cache api tools meet all our needs in that area.

Fragment caching takes place after object caching.  You would request 
results, a request which may or may not populate the object cache, and 
then you do something to those results to prepare them for use or 
display. That result is what I would consider fragment caching as you 
are likely caching a prebuilt HTML fragment that could be used on pages 
as they are being refresh.  It is possible that you can be tolerant of 
the values in that cache for 24hours (or more) and so when a page 
expires from the page cache, it can be rebuilt quicker because some of 
the work has been done already.

Brian Layman

* except query which is part of the object cache mechanisms already

On 7/21/2012 2:07 AM, Otto wrote:
> On Fri, Jul 20, 2012 at 2:08 PM, Mike Schinkel <mike at newclarity.net> wrote:
>>> If you meant a standard _page_ caching API, you should have said so.
>> Also, there are more potential types of caching that _page_ and object caching; there is fragment, query, widget, menu, and http to name a few.
> Except for page caching, aren't all of those pretty much capable of
> being handled with the object cache?
>
>
> -Otto
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers