Zend Framework: Zend_Cache_Frontend_Execpage Component Proposal

Table of Contents

1. Overview

One of the drawbacks of using full page content caching is that while most of a cached page is static there are often small pieces of data on a page that need to change based on the request, for example a "Hello, Name" greeting. Those types of personalization features often force people to use a more complicated caching methodology in order to have personalization, or it forces them to not use it at all.

2. References

• Zend_Cache

3. Component Requirements, Constraints, and Acceptance Criteria

• This component will work like the Zend_Cache_Frontend_Page class in terms of its operation, with the exception that there needs to be a $cache->end() call made, like Zend_Cache_Fronted_Page. This is so embedded PHP can be executed at the end of the request.
• This component will allow a developer to embed PHP in a Zend_View view if MVC is used, or a regular PHP file if Zend_View is not being used, using a special tag. Any PHP code embedded within that tag will be executed for each request
• This component will validate any embedded PHP code against the actual source files, protecting against code injection attacks. If using Zend_View it will validate code only against view components. Otherwise it will only validate against the current main file.

4. Dependencies on Other Framework Components

• Zend_Cache

5. Theory of Operation

In the bootstrap (or other place if caching is not done over the entire application)

6. Milestones / Tasks

• Milestone 1: [DONE] Create caching implementation
• Milestone 2: Mostly [DONE] Create code validation logic
• Milestone 3: Create unit tests

7. Class Index

• Zend_Cache_Fronted_Execpage

8. Use Cases

UC-01

9. Class Skeletons