Thanks for the insight. I started with CakePHP last October so the changes since then have been numberous. In fact, most of the override ability and bootstrapping didn't exist then.
So, in terms of AJAX it probably isn't a good idea to call a requestAction with array return inside a controller. I did this so that the entire content is updated. But I think instead I could just have the method make the content. Then, when it is deleted or altered the AJAX would make the necessary changes. For example deleting a record. OnComplete it should just remove that row via pure javascript instead of requerying the method to get the new entire contents. That should only be done on a page refresh. Very interesting insight now from what you wrote. I guess I never really thought of using requestAction in the view. But now after this discussion and looking at the BakeSale code it does make good sense where it was used. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
