Yes that will work. I've been working on something very similar for an opensocial container, where I use models not tied to a database. I use something similar to this, although I also overrite save so you can validate on save.
http://svn.viney.net.nz/things/rails/plugins/active_record_base_without_table/ Also, the built in json serializer has really bad performance, especially in it's association handling. I used the json gem and wrote my own code for serializing associations. Chris On Wed, Jan 21, 2009 at 5:30 AM, Shak <[email protected]> wrote: > > Hi, > > I'm looking into using RoR to develop a front end for an existing > system - one which is accessible via JSON-RPC. As such, there won't be > any data management performed directly by the web application itself, > all would be done via these RPC calls. > > Is this possible? I assume that it is, so the next question is whether > it's appropriate or not to chop off the model part of Rails. From > tutorials and the like Rails seems quite dependent on convention (and > even boasts of this). Will I get into trouble later on, or will > decoupling the model part be more trouble than it's worth? > > Thanks, > > Shak > > > > --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
