I have only been using this MVC logic since I picked up CakePHP back in
November.  So, now I am wanting to get away from, yes this code works,
to yes this code is nicely and well written.  So, I am looking for
these little things like a method of a controller should do it's job
and not reference other methods.  And specific to CakePHP that it is a
good idea to always use the requestAction() especially since you should
only be making a minimum number of calls per method anyway.

I always pair AJAX with requestAction because that is where I first
discovered how to make AJAX work in CakePHP VERY easily.  So, that is
what I first associated with it.

Something I would also like to discuss is $uses arrays that include
nearly all models.  If you had to pick would you rather make a method
in a controller that calls the findAll and returns it and call via
requestaction or define the model in uses and call $modelName->find or
what have you?  This would allow for easy updating of the controller's
method if additional complexity was needed in the future.


--~--~---------~--~----~------------~-------~--~----~
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