On 9/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > So it doesn't break anything except you said that the callbacks > wouldn't work. And then also what about if you wanted to redirect and > then after the redirect keep processing and actual delete the record > (or something similiar). > > I am just against special case advising. Of course in egineering I > always hated to get all the equations, I just wanted the parent one and > derive whatever one I want from it. So, if return false worked without > messing with callbacks or after the redirect processing why not > recommend that anytime someone mentions calling exit()? > > I am also curious as to how it would render and then render on the > redirect as well.
Well, generally speaking, when I do a redirect that's the last action in a chain I want to do so an exit() makes sense to stop the current action from being executed and get the required one working. I can see circumstances where an exit() wouldn't be required. -- Chris Hartjes "The greatest inefficiencies come from solving problems you will never have." -- Rasmus Lerdorf @TheBallpark - http://www.littlehart.net/attheballpark @TheKeyboard - http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
