Hi Fred,

Sorry, forgot to reply to your question earlier. The problems we had with 
ActiveResource were mostly around situations where the source data structure 
didn't match perfectly with our local data structures. It became a real pain in 
the ass transforming it. I actually found it easier to just use RestClient and 
hydrate the class attributes myself using hand rolled builders. We also had 
services that didn't easily map 1 to 1 with REST. Presumably if you are in 
control of both ends then you can avoid this.

Cheers,

Adam Boas




On 11/03/2012, at 7:15 PM, Fred Wu wrote:

> Just an update:
> 
> I've started building the API service using Darcy Laycock's newly released 
> RocketPants gem: https://github.com/filtersquad/rocket_pants Which works 
> pretty well, but unfortunately using his API Smith 
> (https://github.com/filtersquad/api_smith) as the client isn't as easy as 
> using ActiveResource given the relatively simple RESTful URL structure of the 
> systems.
> 
> So, I've now switched to using RocketPants (for versioning and error 
> handling) + ActiveResource + InheritedResources - works pretty well so far. :)
> 
> Fred
> 
> On Monday, 5 March 2012 04:18:06 UTC+11, Fred Wu wrote:
> Hi guys,
> 
> I'm building a RESTful web service that will be consumed by two clients. To 
> cut down the number of techs/frameworks involved, all three apps will be 
> built in Rails. I'm thinking that I could use Grape for creating the API 
> including versioning, and just use ActiveResource in the clients to consume 
> the service.
> 
> Are there any better/cleaner solutions? I've checked out HTTParty (and 
> API_Smith) but seems like ActiveResource is still a bit easier to work with. 
> Any thoughts?
> 
> Thanks!
> Fred
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby or Rails Oceania" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/rails-oceania/-/6bqhWFaUSNMJ.
> To post to this group, send email to rails-oceania@googlegroups.com.
> To unsubscribe from this group, send email to 
> rails-oceania+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/rails-oceania?hl=en.

-- 
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 rails-oceania@googlegroups.com.
To unsubscribe from this group, send email to 
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Reply via email to