The order they are specified (when matched) then the rest incase non match is fail thus stops the rest....presuming my understanding of what you ask is correct. Without further expeiences and:or guidlies for the usage of this feature it's hard to say as a lot of this stuff I'd discovered through trial and error. Which usually isn't an ideal way to discover things as you can never be sure about what you discover. And being sure is important. Would actually need to see the source with the samples and full explanations before even considering giving a convincing answer as the question makes no sense to me and I've no way of finding out exactly what the possible scenarios are. This should be easy to answer IMO whether it's been used once or a hundred times. I must be missing something pretty major otherwise.
Kindest regards. Sent from iPhone On 17 Mar 2009, at 14:48, Felix Gilcher <[email protected]> wrote: > Hi Folks, > > since the last routing refactoring a single route can have multiple > callbacks that are executed in the order in which they are defined. > David, Dominik and me just ended up in discussion whether it might > be reasonable to revert that order when generating an url. That is > when a route is (not) matched on(Not)Matched is called in the > defined order and when a url is generated, onGenerated is called in > the reverse order. That would allow for callbacks depending on each > other. > > So we'd like you guys to answer two questions: > > - What do you think which order is reasonable? > - Does anybody currently rely on the current execution order? > > cheers > > felix > _______________________________________________ > Agavi Dev Mailing List > [email protected] > http://lists.agavi.org/mailman/listinfo/dev _______________________________________________ Agavi Dev Mailing List [email protected] http://lists.agavi.org/mailman/listinfo/dev
