Whoops! I responded in the wrong thread... :)
On Fri, Dec 16, 2011 at 2:56 PM, damien krotkine <[email protected]>wrote: > Well your code will stil work, no need to change anything > > > On 16 December 2011 13:33, Nick Knutov <[email protected]> wrote: > > I always do something like > > > > return redirect '/error/?reason=...' unless pass_all_checks() > > > > I think I read in documentation or examples that it should be so and this > > way looks better - I can decide how it will work. > > > > I think it's better to make accent on using 'return' when it needed, not > > changing behavior. > > > > 16.12.2011 18:16, damien krotkine пишет: > > > >> On 16 December 2011 12:57, Nick Knutov<[email protected]> wrote: > >>> > >>> +1. > >>> > >>> As pass() and other. > >>> > >>> Btw, are any reasons at all to halt the execution of the route handler > in > >>> this functions? > >> > >> > >> There were a nasty security issue that if you uses a hook to catch the > >> fact that a user is not authenticated for instance, the workflow would > >> still continue in the rest of the route, so we needed a way to stop > >> the execution of the route code block only. > > > > > > -- > > Best Regards, > > Nick Knutov > > http://knutov.com > > ICQ: 272873706 > > Voice: +7-904-84-23-130 > _______________________________________________ > Dancer-users mailing list > [email protected] > http://www.backup-manager.org/cgi-bin/listinfo/dancer-users >
_______________________________________________ Dancer-users mailing list [email protected] http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
