Hi Folks, I'm in the design stages of a fairly standard new Rails project that calls for two applications - one for staff and one for customers.
The data model for each is identical, and initially at least they will be hosted on the same machine. The way I've approached this in the past is to share models between the apps and point them at the same database. This will work, but it strikes me as the kind of scenario ActiveResource is designed to be used in. ActiveResource has always seemed the poor cousin of the Rails world to me and I've never used it. Does anyone? Is it worth looking into? Know of any ActiveResource success (or failure) stories? -- James Healy <[email protected]> Fri, 02 Oct 2009 12:13:48 +1000 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
