Depending on how close that backend interface is to what Rails expects from it, you can either get a seamless integration with ActiveResource [1], or dig deeper and just build your model as ActiveModel, leveraging modules provided by Rails 3 to quickly add stuff like validations, and replacing persistence with your own code that talks to your backend. For example, using the latter approach I integrated recently with IIS and its SOAP interfaces, using them instead of a database as the backend for some models.
Documentation for ActiveModel is quite lacking, though, so in my experience getting familiar with the relevant parts of Rails code will let you get it up and running much faster. [1] http://api.rubyonrails.org/classes/ActiveResource/Base.html -- 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.
