-- Roman1975 <[EMAIL PROTECTED]> wrote
(on Monday, 10 December 2007, 05:11 AM -0800):
> 1000 times sorry this is correct, and works

No worries. :-)

> so perhaps loop if there is a circular requests action but it is easy
> to correct.

The action() view helper does not loop; it dispatches exactly one
action. (The dispatch loop is within Zend_Controller_Front::dispatch(),
and we're not using that to dispatch the action, but instead going
directly to the dispatcher.)

> Matthew Weier O'Phinney-3 wrote:
> > 
> > -- Roman1975 <[EMAIL PROTECTED]> wrote
> > (on Monday, 10 December 2007, 12:30 AM -0800):
> >> The front controller is a singleton, and as such should not allow
> >> cloning, to this end, we added a private __clone () method.
> >> 
> >> 
> >> But these very possible you did not challenge Helper View
> >> $ this-> action!
> >> Plus you have banned the possibility of establishing parallel challenges
> >> to
> >> any action, you are sure that this is true? Because of the loss of
> >> flexibility.
> > 
> > It is only the Front Controller itself that is a singleton. The various
> > other objects it consumes are *not* singletons -- including the plugin
> > broker, request and response objects, router, dispatcher, plugins, and
> > action controllers. 
> > 
> > Zend_View_Helper_Action, as I mentioned in a previous email, clones the
> > *dispatcher*, as well as the request and response objects, in order to
> > do its work. All of these can be cloned without issues. We do not
> > dispatch a secondary front controller as (a) it's not necessary for the
> > scope of this particular helper, and (b), this would likely lead to race
> > conditions.
> > 
> > If you ever have doubt about whether or not code in ZF works, *please*
> > run the test suites. These exercise the code fairly rigorously.

-- 
Matthew Weier O'Phinney
PHP Developer            | [EMAIL PROTECTED]
Zend - The PHP Company   | http://www.zend.com/

Reply via email to