On Friday, 29 June 2012 14:21:39 UTC+2, Dr. Tarique Sani wrote:
>
> Err... Larry, the book warns "If used without caching requestAction
> can lead to poor performance.
I added that warning - as with 1.3 there was a noticable performance
penalty using request action.
It is rarely appropriate to use in a controller or model."
That part holds true no matter what, as it relates to application
architecture. The valid use-cases for request action are few and far
between.
After all, why do this:
x > Dispatcher > Routing > Controller > Model->data()
to get data when you can just do:
x > ClassRegistry::init('SomeModel')->data()
That's 3 parts of the application stack removed at absolutely no loss of
functionality in a typical fat-model application.
Doing something similar to ESI (i.e. any kind of dynamic multi-part page,
the subject of the first post) is one of the few cases where requestAction
is a good fit.
> and I can attest to poor performance of RA
>
I am guessing you're remembering/referring to data from 1.3 - benchamarking
request action with 2.x some time ago there was absolutely no cost to using
request action in and of it self.
AD
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.
To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/cake-php
