@Amit: I thought the same thing, but you can't really return something to the browser from a Component
@j0n4s: It's not speed, it's having one controller that handles typical generic requests, so that you don't have ajax_* actions in 15 or so different controllers Adam On Oct 20, 7:56 am, "[email protected]" <[email protected]> wrote: > I would not want to break the basic MVC paradigm because I just can, > though I admin thinking about live validation (of form fields) to add > some additional php file like ajax.php which handles some model > construction and validation checking without ever running a full cake > stack. Besides that I wonder why you want to manage all ajax requests > through one controller?! If You really fetch complete models via > controllers and display them via views, make them modifyable, why not > trigger a full cake request there? If its speed, maybe caching helps > as well. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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?hl=en -~----------~----~----~----~------~----~------~--~---
