Issue Type: Improvement Created: 2010-04-02T13:32:48.000+0000 Last Updated: 2010-10-12T10:06:50.000+0000 Status: Resolved Fix version(s): Reporter: Brandon Savage (brandonsavage) Assignee: Pádraic Brady (padraic) Tags: - Zend_Application
Related issues: Attachments:
Presently, in order to use the cache, one must disable Zend_App's own output buffering in the following fashion (also for using Zend_Cache_Page):
resources.frontController.params.disableOutputBuffering = true
However, this is not documented. After talking with MWOP it was his suggestion that the cache automatically do this on behalf of the user.
Posted by Brandon Savage (brandonsavage) on 2010-04-05T16:52:54.000+0000
Assigning to the author of that component.
Posted by Pádraic Brady (padraic) on 2010-04-29T08:26:02.000+0000
Will talk to Matthew for surety - I can't remember from the maze of Zend_Controller what impacts this has/does not have in relation to other components. Worse, I haven't the slightest idea how Zend_Cache can go off the reservation to impact Zend_Controller like that. Sounds like a static FC call which I really don't want to add to an independent component. What does worry me is why is it not documented? I could swear I submitted these in the docs, and even edited the Page docs to reflect it.
Posted by Pádraic Brady (padraic) on 2010-04-29T08:30:44.000+0000
It's documented for the Page Frontend (in a note). I'll add in the Capture frontend in a while - must have missed a commit somewhere when I was adding these notes.
Posted by Pádraic Brady (padraic) on 2010-10-12T10:06:50.000+0000
The required setting is documented, but imposing a coupled call between two components is not a good idea (at present). Maybe ZF 2.0 will make this easier.
Have you found an issue?
See the Overview section for more details.