Yes, it certainly helps to understand your reasoning. On May 14, 9:50 pm, José Lorenzo <[email protected]> wrote: > If you think about it, collecting return values is actually the edge case: > > A save operation has a single result wich is data to be saved > > A redirect operation has a single result, the URL to redirect to > > A dispatching operation has a single response value as result > > There a very few cases where collecting the result is desired, an it is often > the consequence of a wrong software design. If you want to collect return, > pass an object as parameter and have listeners modify this object at will. > > An example of this type of callbacks is JavaScript, an events language, wich > usually don't take in account result values for events but 'false'. If you > want to alter any result you should be modifying an object. > > I hope my answer helps understand the resonance we had for making the event > system work this way.
-- 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
