Zend Framework: Zend_Cache_Frontend_Page Component Proposal
| Proposed Component Name | Zend_Cache_Frontend_Page |
|---|---|
| Developer Notes | http://framework.zend.com/wiki/display/ZFDEV/Zend_Cache_Frontend_Page |
| Proposers | Kevin Schroeder |
| Revision | 1.0 - January 23 2008 (wiki revision: 9) |
Table of Contents
1. Overview
Adds ETag support for Zend_Cache_Frontend_Page
2. References
3. Component Requirements, Constraints, and Acceptance Criteria
Component will implement ETag support by default for any HTTP request with an If-None-Match header field
4. Dependencies on Other Framework Components
- Zend_Cache
5. Theory of Operation
Zend_Cache_Frontend_Page will generate an Etag for the page content in a given request. Subsequent requests from a browser that have a matching ETag for the content currently in the cache will receive a 304 HTTP header code instead of the actual cached content.
6. Milestones / Tasks
Undefined as of yet
7. Class Index
- Zend_Cache_Frontend_Page
8. Use Cases
9. Class Skeletons
diff code
ZF Home Page
Code Browser
Wiki Dashboard
I would like to work on an HTTP cache.
You should think about the response object for the headers, Zend_Cache_Frontend_Page acts after the response is sent so it should be allright but perhaps an MVC plugin would be needed ?
I think we should as well be able to controler the cache-control to prevent proxies from caching some pages, shouldn't we ?
last thing : Zend_Cache_Frontend_Page has already got some support for such a HTTP cache system, see 'http_conditional' in it.