Ryan's Scraps

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: rails, rubyonrails, REST

I just ran across an almost exact functional clone of my RailsDay entrant, Gr.egario.us over at Quotiki. I’d say the design is much better than what I was able to do, although they don’t yet have the ability to put quotes on your own site like gr.egario.us offers.

Is that the sound of bitterness you hear? Not at all – in fact I’d love to pull gr.egario.us down at some point so please take a look at Quotiki for your future needs. My only question is – was Quotiki written in a day?

If any of the Quotiki folks want to look at how easy it is to write in Rails, let me know and I can shoot the source over to you. The only thing more satisfying than a Java-to-Rails conversion is a .NET-to-Rails conversion.

tags: rubyonrails, rails, railsday2006, quotiki

It’s gotta be right around the corner, right?