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 <[email protected]> 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 [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. > -- 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.
