My 2 cents, try keeping your models as fat as possible. This way your models can be used from your controllers or opened to third party (just creating an ApiController for example) reusing the logic.
Regards, -- Pablo Viojo [EMAIL PROTECTED] http://pviojo.net On Wed, Mar 5, 2008 at 5:08 PM, Sonic Baker <[EMAIL PROTECTED]> wrote: > > > On Tue, Mar 4, 2008 at 2:16 AM, mbavio <[EMAIL PROTECTED]> wrote: > > > > > > > this is a good place to > > starthttp://particletree.com/features/how-to-add-an-api-to-your-web-service/ > > > > > > look at the additional reading section at the end > > > > > > Sam D > > > > I was actually thinking and discussing this topic myself lately. Then I > was wondering, if I create an API, should I change my application to > actually use the API itself, i.e. should I have a kind of core with an API > layer on top and then code the rest of my app to work through the API. Would > this be overkill or would it have it's benefits? > > Thoughts? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
