A few weeks back I posted a <a href="http://www.mikenicholson.net/2008/12/what_rails_could_do_better.php">vent blog entry</a> about some shortcomings of Ruby. Well, it looks like one of my concerns has been at least partially resolved.
<a href="http://dev.ctor.org/">Hiroshi Nakamura</a> created, and continues to maintain, a wrapper around Net::Http called <a href="http://dev.ctor.org/http-access2">httpclient</a> which adds enough functionality to save lots of time. Sure the performance still sucks compared to curl, but with this great library you can do <a href="http://dev.ctor.org/doc/httpclient/classes/HTTPClient.html#M000015">multipart form posts</a> and <a href="http://dev.ctor.org/doc/httpclient/classes/WebAgent/Cookie.html">basic cookie functionality</a>. Now my rails app can finally make use of some more complex HTTP based APIs out there (not everything is simple REST).
<a href="http://dev.ctor.org/">Hiroshi</a>, you rock, but back to my other complaint about Ruby stuff being scattered about the wind, please submit your gems to one of the big repositories so we can find them :)
<a href="http://dev.ctor.org/">Hiroshi Nakamura</a> created, and continues to maintain, a wrapper around Net::Http called <a href="http://dev.ctor.org/http-access2">httpclient</a> which adds enough functionality to save lots of time. Sure the performance still sucks compared to curl, but with this great library you can do <a href="http://dev.ctor.org/doc/httpclient/classes/HTTPClient.html#M000015">multipart form posts</a> and <a href="http://dev.ctor.org/doc/httpclient/classes/WebAgent/Cookie.html">basic cookie functionality</a>. Now my rails app can finally make use of some more complex HTTP based APIs out there (not everything is simple REST).
<a href="http://dev.ctor.org/">Hiroshi</a>, you rock, but back to my other complaint about Ruby stuff being scattered about the wind, please submit your gems to one of the big repositories so we can find them :)
