Developer Notes -- Fragment Caching

Due for release in version 0.8.

Documentation -- Overview with generic examples

Source

Browse source: /branches/fragment-caching

Subversion checkout:  http://svnpub.armadillo.homeip.net/wp-supercache-plus/branches/fragment-caching/

Currently Testing

[608] Experimental: Variable TTL on fragments based on nested depth

1. Outer fragments expire first, but can be rebuilt from non-expired nested fragments.
   The issue still remains however, that when the outer fragments expire, page generation time is likely¹ back to what WordPress? can deliver.

On the basis of my preliminary musings on (1), it seems that there may still be value in persisting with wpscp_use_cached_fragment() which attempts to spread the load of fragment regeneration over time. This currently has a similar weakness; outer fragments tend to protect the nested ones from being selected for regeneration.

Blue Sky

Stagger expiry time of fragments produced by a single request

This is a possible alternative to wpscp_use_cached_fragment() post-hoc method of not having everything for a single page expire at the same time.

Problems:

• Number of fragments not knowable (???) in advance

Benefits:

• Shifts processing from retrieval (we want fast) to storage (is already slow)

TODO

Known Issues

status accepted

#4

Fragment Caching does not support WP2.7+ wp_list_comments()

#5

Fragment Caching not Supported when using 'Disk Storage'

status new

#6

Add ready to use fragment cached version of WordPress default theme

---

1. 1. It is possible that another outer context will have regenerated inner fragments