Thanks guys for the suggestions and comments! @Ben: I did briefly consider using engines but at the end of day, services make more sense. The service itself isn't a module of the clients, it is almost the foundation of the clients, it warrants to be separated from the clients imo. Thanks for the heads up re Grape, I might skip using it if it doesn't play nicely with the other gems. This morning I just discovered Versionist, which looks like just what I need for API versioning.
@Simon: Anything in particular that you found difficult to do in ActiveResource? I had a look at your Resty gem, it's very nice, though I don't really need the self-discovery feature, so it probably is overkill for me. @Gareth: Oh, really nice! Thanks for the article! If I do end up using ActiveResource, I'd definitely implement this for caching. :) @Adam: I have total control of the service as well as the clients consuming it, so I imagine it wouldn't be too big of an issue in terms of working around AR's limitation (I could be wrong). The same question I asked Simon - anything in particular that you found difficult to do in ActiveResource? Thanks! 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 > 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/-/lOSRJANwEzMJ. 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.
