Fred, ActiveResource is pretty good and very easy to work with. One thing you will probably need to do is write your own caching strategy around it, there's no support for http caching headers built in sadly.
When I was at NZX, we ended up writing a read-through cache on our client side as our application was very read heavy. More info here: http://injectisforwizards.com/blog/read-through-caching-of-activeresource/ On 05/03/2012, at 9:07 AM, Simon Russell wrote: > I haven't had great success with ActiveResource, but I guess if you > tune the APIs to meet its fairly limited abilities, it might work. > > I'd say use the gem I made for consuming REST APIs of a particular > design, but it's a bit unfinished :) Did work somewhat nicely in most > situations though. > > Simon. > > On Mon, Mar 5, 2012 at 08:01, ben wiseley <wisel...@gmail.com> wrote: >> Hey Fred! >> >> If you have control over all three apps and this api isn't going to be used >> by an unknown third party I'd really consider going the engine route instead >> of the API route. It'll be a lot faster in the long run and be one less >> server you need running. >> >> I started using Grape on an API but ended up going straight Rails in the >> end. Grape's great if you're doing simple stuff but getting it to play nice >> with things like Devise is pretty hackity-hack. >> >> -ben >> >> >> On Mon, Mar 5, 2012 at 4:18 AM, Fred Wu <ifre...@gmail.com> 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/-/Hg2WDp82a9oJ. >>> 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. > > -- > 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. > Cheers, Gareth Townsend http://www.garethtownsend.info -- 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.
