I'm using cake 1.1.4, dealing with a requestAction problem. In one of my controllers I need to apply some logic which clearly belongs to another controller, to do this, I used a requestAction. The abuse of this feature quickly brings a significant drop in performances.
In my opinoin, moving the login from controller to model to then be able to load the model in the other controller and perform the checks is wrong, models are not the place for such things, correct me if I am wrong. The duplication of such logic in every controller where this is needed doesn't sound right to me either. In a situation like mine, what would be the best way to access another controller's logic? Is there somewhere you can point me to? Thank you Repsah --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
