Re: Re: exit() after redirect

Thu, 21 Sep 2006 22:15:18 -0700

It's funny I the first time I remember seeing someone recomending this approach was in response to 
someone who wanted to know how to have cake stop doing anything after the redirect, and it soon 
became the standard way to tell people how to do it.

Sam D

On 9/21/06, Mika <[EMAIL PROTECTED]> wrote:

This is exactly why I asked the question in the first place.

I see that exit() seems to be recommended all over the place, but
people should realise that it will stop the flow of cake totally at
that spot. This is usually not a problem, as Nate said, but if you've
set some callbacks or something it could be. Just because you're
redirecting does not mean you don't want the code to finish.

For example what if you've got some logging going on or something after
an action. On exit this code would never get executed.

So in other words, exit() is not any better or worse than return but
people should just understand the consequences.



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---

Reply via email to