What's New in Edge Rails: ActiveResource Pulled from v1.2, World Weeps

Posted by ryan
at 8:07 AM on Monday, November 20, 2006

The REST client framework, ActiveResource, has been pulled from the up and coming Rails v1.2 release.

I’ve been using it to develop some REST client libraries and there are some refinements I can see being needed, but I don’t know if that’s the reasoning for its exclusion in the up-coming release. As a quick refresher – ActiveResource is the client framework that lets you invoke REST services from model objects. Think of it as ActiveRecord for REST.

However, get your REST panties out of their collective knot – you can still develop completely RESTful apps using the Simply RESTful server side functionality and the link helpers for enhancing the web tier with REST compliant requests.

Thanks to Tom of GiftHat for beating my feedreader to the punch on this one.

tags: , ,

Comments

Leave a response

  1. josh – November 20, 2006 @ 08:30 AM
    I don't believe that ActiveResource has been *pulled*. It just hasn't been promoted to a released component. The code will still be available in edge, though. Personally, I doubt we'll see a release of ARes before 37sig releases a product that uses it.
  2. Ryan Daigle – November 20, 2006 @ 08:37 AM
    It's definitely been _"pulled from ... Rails v1.2"_ - but you're right about it still being available in edge rails.
  3. Ryan Daigle – November 20, 2006 @ 08:37 AM
    Ah - I see now Josh - the title is a bit misleading. Let's see what I can do about that.
  4. rick – November 20, 2006 @ 08:38 AM
    It was never part of Rails. I don't think we'll see a release until we see some good real-world usage.
  5. rick – November 20, 2006 @ 08:39 AM
    Though, I realize that's kinda chicken-before-the-egg. Want to see a release sooner? Start using it and pounding on it so we can get things nailed down and work the quirks out.
  6. Ryan Daigle – November 20, 2006 @ 10:21 AM
    I hear ya Rick, and I'm trying as we speak...
  7. DHH – November 20, 2006 @ 11:45 AM
    Josh is right. It's a mistake that ARes was ever included in the 1-2 branch. Simply a matter of not taking it out sooner after doing "svn cp trunk branches/1-2-pre-release". So no big drama ;)
  8. DHH – November 20, 2006 @ 11:45 AM
    Also, the decision as to whether ARes will _ever_ be part of core Rails has not been made yet. So it's not even sure it'll be included in Rails 2.0.
  9. Ryan Daigle – November 20, 2006 @ 02:44 PM
    And so it shall live in edge ad-infinitum...
  10. Jason – November 20, 2006 @ 11:19 PM
    "The decision as to whether ARes will ever be part of core Rails has not been made.." Is there any reason at all against including it? It's not a compulsory feature of the framework, you could include it and let people choose for themselves?
  11. David – November 21, 2006 @ 01:13 AM
    Jason: I think the point is that core are trying to strip Rails down to the bare essentials for Rails 2 and then allow people to extend with plugins as they wish. Therefore, as ActiveResource is not a compulsory feature of the framework, why include it when people can just add it themselves if they know they need it? I think the way things are going (removing ActionWebService as well) will ultimately help Rails core to stay trimmed down to what it does best and help to avoid it becoming some overblown one size fits all framework.
  12. Timo Mika Gläßer – December 04, 2006 @ 10:45 AM
    It would actually be nice though to have an nicer way to integrate additional frameworks into rails like in "environment.rb".
  13. topfunky – December 05, 2006 @ 02:05 PM
    @Timo: Like "require 'some_library'"? The RubyGems system is great for that. Or do you mean something more like the gem_plugin system in Mongrel that is more automatic?