There is nothing in controllers and views that assumes active record
for the model, and the model knows nothing about the other 2. That is
what separation of concerns is all about. You can build model classes
any way you like. The classes should provide some form of class level
methods the controller can use to get started servicing a request. It
may or may not return instances of the "model" class, or just data in
other forms like hashes and such.
Michael
On Jun 15, 10:58 pm, murtada
<murt...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> Hi,
>
> I am accessing a web service that sends me a list of events. My local
> ROR application is an events website.
>
> What is the best way to integrate these? If I were to have a local DB,
> I would just create a model, controller etc. Is it possible to keep
> such a structure, and just have the model retrieve data from the web
> service instead of the local DB?
>
> Thanks.
>
> Murtada
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---