Zend Framework: Zend_Cache backend for eAccelerator Component Proposal
| Proposed Component Name | Zend_Cache backend for eAccelerator |
|---|---|
| Developer Notes | http://framework.zend.com/wiki/display/ZFDEV/Zend_Cache backend for eAccelerator |
| Proposers | Federico Cargnelutti |
| Revision | 1.0 - 16 August 2008: Initial Proposal. (wiki revision: 4) |
Table of Contents
1. Overview
The eAccelerator backend for Zend_Cache would allow developers to use eAccelerator content caching capabilities with Zend_Cache class.
2. References
3. Component Requirements, Constraints, and Acceptance Criteria
- This backend would allow to store and retrieve data in the eAccelerator shared memory.
4. Dependencies on Other Framework Components
- Zend_Cache_Backend
- Zend_Cache_Backend_Interface
5. Theory of Operation
The backend will use eAccelerator functions eaccelerator_get, eaccelerator_put and eaccelerator_rm to retrieve, store and delete information from the cache.
6. Milestones / Tasks
- Write proposal
- Gather feedback
- Review by the Zend team
- Develop full implementation and unit tests
- Documentation
7. Class Index
- Zend_Cache_Backend_Eaccelerator
8. Use Cases
| UC-01 |
|---|
9. Class Skeletons
Labels:
None
4 Comments
comments.show.hideAug 31, 2008
Nikolay Mogulev
Zend_Cache_Backend_Apc is perfect source for eAccelerator backend. One difference that eAccelerator can support Zend_Cache::CLEANING_MODE_OLD cleaning mode.
ps. already made eaccel backend for own project
Aug 31, 2008
fc
Yes, that's the idea, they all implement Zend_Cache_Backend_Interface. Like you said, it's a very straight forward proposal. I'll move it to the "ready for review" section next week.
Oct 06, 2009
Justin Hart
Where along the path is this proposal? Is there a need for an implementation?
Dec 16, 2009
Marc Bennewitz (GIATA mbH)
The latest rc doesn't support user cache and is the only one which supports PHP 5.3
Jul 14, 2009 - Bart Vanbrabant
------------------------------
The theme of this release is: back to basics! All non essential functions
are removed from eAccelerator. This means that the optimizer and the
keys, content and session functions.
Changes in this version: