Web service client code layout -- standard practice

rubyonrails-talk
1

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.

2

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.

3

Curtis Schofield wrote:

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.

Thank you. Will see the mentioned gem.

4

I guess ActiveResource is restrictive if you don't have control on the WebService API.

Net::Http is most flexible but no parsing done for you.

Httparty seems nice. It uses Crack gem for XML parsing, that is better than Rexml and Hpricot in terms of parsing I think. Of course, libxml is the fastest but this good too.

In the end, use depending on what works for you based on your requirements.

5

Smart RoR wrote:

I guess ActiveResource is restrictive if you don't have control on the WebService API.

Net::Http is most flexible but no parsing done for you.

Httparty seems nice. It uses Crack gem for XML parsing, that is better than Rexml and Hpricot in terms of parsing I think. Of course, libxml is the fastest but this good too.

In the end, use depending on what works for you based on your requirements.

And yes, Httparty uses Net:Http under the hood, so you know it is reliable for the basic calls....:slight_smile: