Hi TWIOF, I don´t know what your app looks like but: 1) controller/component code as my previous message 2) Model something like this: http://www.cakephp.org/pastes/show/87a51730f72c38147dcc40b086f08b3a
Model methods: a model is a just a class like any other - create the method. The methods your model has by default are inherited (via the class it extends) and you can see all of them here: https://trac.cakephp.org/browser/branches/1.1.x.x/cake/libs/model/model_php4.php Speed: noticably, it won't be a problem while you are testing but having the server processing 8 times as many requests as displayed pages is bound to take an effect :). The view should never need to ask for anything it should always receive info - as such using requestAction to get an identifier or the likes is quite anti MVC. Logic: have a look at what requestAction does - it is virtually the same as typing the url in your address bar, as such it has an overhead in setting up objects etc. If your question was more about moving code, if you consider the lines of code in the order they are going to be executed I am only suggesting moving lines of code that are in your controller to the model - as such no difference from that perspective. Personally I try to 'push' code and variables as close to where they are needed as possible. e.g. no html ever in a controller, no logic in a controller that could be placed in a model. I'm not the most experienced developer on this list but if you are still struggling you can find help here: http://irc.cakephp.org/irc.html Cheers, AD7six --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
