You might like httparty for this (instead of Net:Http)
I think a good place - if you are only doing it it one place - is the model you use it in - with a test around that model. If you are doing more than that and you are building a tool for this then the lib directory. On Sun, Feb 28, 2010 at 7:59 AM, Smart RoR <[email protected]> wrote: > Hi: > > Where do you all think the web service client code (for a REST service) > access fit in a Rails App? > Models are what Controllers call and should probably do so now also even > though its Non-Active Record. > > However, Models use the web service REST Access code to get XML and > parse it to give ActiveRecord style responses to controller. > > Where should the Net:Http connection style requests be made-- > in lib or initializer requiring lib or as create as a new plugin? > > Where does the parsing of XML code happen-- in Model Itself? > > Is the Rails Helper directory directed more towards views helpful here? > > > Getting it done could be easy to do everything in controller. However, > want to make it more well designed and scaleable from future > perspective. Hence, above code layout questions. > > > Please advise based on experiences. > > Thanks in Advance. > -- > Posted via http://www.ruby-forum.com/. > > -- > 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]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- 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.
