If you want to avoid overhead, you should better use
- Zend_Controller_Action_HelperBroker::removeHelper('viewRenderer');
instead of 
- setParam( 'noViewRenderer', true )


Shekar C Reddy a écrit :
Hi All,
 
For those who use third-party templating engines and don't wish to use the ViewRenderer helper (and even Zend_View), its additional over-head of invoking methods such as setParam( 'noViewRenderer', true ), the auto-addition of the helper object itself to the helper broker stack, file I/O, latency, its various internal initializations, etc. do not make any sense - not to mention it would likely degrade performance! However, for those who wish to use its functionality, they could always invoke setParam( 'viewRenderer', true ). One line of code in the boot-strap would make its entire processing over-head sense to those who wish to use it.
 
IMO, features should be incorporated in a generic way and should apply to only those who wish to use them rather than auto-enable them (instantiate/register) by default only to be disabled by those who don't need them - it tantamounts to superfluous processing. Its like auto-enabling/registering objects such as Zend_Cache, Zend_Config, Zend_Session, etc. in the registry and then expect the developers to disable them if they don't wish to use them.
 
Thoughts?
 

Reply via email to