On 07/12/2011, at 2:49 PM, Chris Berkhout wrote: >> I tried to stay within MRI, but the REST API just isn't good enough. So I >> quit on it. > > Not good enough in terms of features? > I guess it's more Java, but extending the API may be an option.
Yes, features. There are couple of gems that help with it: neology (not maintained, failing specs), architect4j (ActiveRecord-like, new project, some failing specs). I even thought to come up with something better. But then I realised it's not that simple. Those abstractions are leaky and the best bet is to stay as close to the HTTP request/response as you can. While, with native bindings, you can traverse the graph natively from ruby. And it's is pretty efficient. With REST you'd have to run traversal queries for that. It basically means that anything more or less complicated involves a number of HTTP req/resp and wrapping all that with your models. -- 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.
