You should create a new APIModel, for example, that your Model extends so it encapsulates all the logic needed to communicate with your system through the API. This way you can use the model in the same way you used the "normal" ones.
Depending on the complexity of the API it can be more or less difficult to implement but in the end all you have to do is create methods for the model operations that respect the cakephp "interfaces" defined. Regards, -- Pablo Viojo [EMAIL PROTECTED] http://pviojo.net On 2/6/07, Chris Hartjes <[EMAIL PROTECTED]> wrote: > > > On 2/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Can I replace the mechanism from the Model that directly interacts > > with the database with specific API functions already in place in our > > existing application. > > You can create models that don't do database stuff, that's for sure. > I'm not sure about redefining existing methods etc. I think it's > doable, but you may have to tweak things at your end to be able to > reference the model data the same way Cake lets you do with data > obtained from a database. > > -- > Chris Hartjes > > My motto for 2007: "Just build it, damnit!" > > rallyhat.com - digitial photo scavenger hunt > @TheBallpark - http://www.littlehart.net/attheballpark > @TheKeyboard - http://www.littlehart.net/atthekeyboard > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
