© Copyright 2009-2010 Sidu Ponnappa. All Rights Reserved.
Wrest is a ruby REST client library which
-
allows allows you to quickly build object oriented wrappers around any web service
-
is spec driven, strongly favours immutable objects and avoids class methods and setters making it better suited for use as a library, especially in multi-threaded environments
-
runs on Ruby 1.8, 1.9 and JRuby, with MacRuby and IronRuby support on the way
To receive notifications whenever new features are added to Wrest, pleasesubscribe to my twitter feed.
(If you were wondering why the words ‘demon’, ‘chi’ and ‘fu-puppies’ show up in nearly every example and spec, it’s because they’re all references to Roger Zelazny’s last book, ‘Lord Demon.’)
-
Provides convenient HTTP wrappers, redirect handling, serialisation and deserialisation with response caching in the works
-
Supports using either Net::HTTP or libcurl as the underlying HTTP library
-
Designed to be used as a library, not just a command line REST client (fewer class/static methods, more object oriented)
-
Isn’t coupled to Rails (usable in a pure Ruby application to consume any HTTP/REST api)
-
Can be used both stand alone as well as to build object oriented abstractions around resources and web services (Wrest::Resource is an example of the latter)
For Facebook, Twitter, Delicious, GitHub and other API examples, see github.com/kaiwren/wrest/tree/master/examples
The source is available at git://github.com/kaiwren/wrest.git
To install as a Rails plugin, do script/plugin install git://github.com/kaiwren/wrest.git
To install the Wrest gem, do (sudo) gem install wrest.
Wrest is also available as a gem for JRuby; you can install it by running (sudo) jruby -S gem install wrest.
You can launch the interactive Wrest shell by running bin/wrest if you have the source or invoking wrest from your prompt if you’ve installed the gem.
$ wrest >> y 'http://twitter.com/statuses/public_timeline.json'.to_uri(:timeout => 5).get.deserialise
require 'rubygems' require 'wrest' y "http://search.yahooapis.com/NewsSearchService/V1/newsSearch".to_uri.get( :appid => 'YahooDemo', :output => 'xml', :query => 'India', :results=> '3', :start => '1' )
A couple of ways to get Yahoo news as a hash map.
-
This example simply does a get on a uri and figures out the appropriate deserialiser using the content-type (in this case ‘text/javascript’, which uses Wrest::Translators::Json). See content_types.rb under lib/wrest/mappers/translators.
"http://search.yahooapis.com/NewsSearchService/V1/newsSearch?appid=YahooDemo&output=json&query=India&results=3&start=1".to_uri.get.deserialise
-
This example does a get on a base uri with several parameters passed to it, resulting in a uri essentially the same as the one above. It also shows how you can specify a custom deserialiser to produce a hash-map from the response, as well as a hash mutator to clean up the deserialised hash.
require 'rubygems' require 'wrest' include Wrest::Components y "http://search.yahooapis.com/NewsSearchService/V1/newsSearch".to_uri.get( :appid => 'YahooDemo', :output => 'xml', :query => 'India', :results=> '3', :start => '1' ).deserialise_using( Translators::Xml ).mutate_using( Mutators::XmlMiniTypeCaster.new )
To delete a resource:
'https://api.del.icio.us/v1/posts/delete'.to_uri( :username => 'kaiwren', :password => 'fupupp1es' ).delete( :url => 'http://c2.com' )
To find out what actions are permitted on a URI:
'http://www.yahoo.com'.to_uri.options.headers['allow']
Allows any class to hold an attributes hash, somewhat like ActiveResource. It also supports several extensions to this base fuctionality such as support for typecasting attribute values. See examples/twitter.rb and examples/wow_realm_status.rb for more samples.
Example:
class Demon include Wrest::Components::Container always_has :id typecast :age => as_integer, :chi => lambda{|chi| Chi.new(chi)} alias_accessors :chi => :energy end kai_wren = Demon.new('id' => '1', 'age' => '1500', 'chi' => '1024', 'teacher' => 'Viss') kai_wren.id # => '1' kai_wren.age # => 1500 kai_wren.chi # => #<Chi:0x113af8c @count="1024"> kai_wren.energy # => #<Chi:0x113af8c @count="1024"> kai_wren.teacher # => 'Viss'
The Wrest logger can be set and accessed through Wrest.logger and is configured by default to log to STDOUT. If you’re using Wrest in a Rails application, you can configure logging by adding a config/initializers/wrest.rb file with the following contents :
Wrest.logger = ActiveRecord::Base.logger
Standard options are available and can be listed using rake -T. Use rake:rcov for coverage and rake:rdoc to generate documentation.
Wrest RDocs can be found at wrest.rubyforge.org
Wrest::Resource is an alternative to Rails’ ActiveResource. It targets Rails REST (well, POX, since Rails isn’t really RESTful) services and is currently under development. Since no single REST library can provide an object oriented wrapper suitable for all available web services, it follows that Wrest should focus on providing you with the tools to 7107 help you roll your own. Wrest::Resource is an example of this - an object oriented wrapper for the kind of REST APIs exposed by Rails applications, that you would otherwise use ActiveResource to consume.
If you’re looking for help doing this on Rails on the server side, take a look at resource_full, a Rails plugin that makes RESTful Rails a whole order of magnitude easier. resource_full is a stable project and is currently in use in production.
-
No more pretending that REST resources are the same as records in a database (yeah, no more freaking ActiveResource::Connection that pretends it’s a DB connection)
-
Treat put as ‘create or update,’ not just ‘update’
-
Response codes result in user defined state transitions; favours state transitions based on response code over arbitrary ones
-
Supports moving toward hypermedia links as opposed to client server collusion through URI templates
-
The header is now exposed as metadata, rather being than something you have no control over
-
Out of the box support for If-Unmodified-Since/If-Match+Etag
-
Out of the box support for collections
-
Out of the box support for collection pagination (including support for WillPaginate), both header based and xml attribute based
-
Out of the box support for operations on all the records on the collection
-
Out of the box support for nested resources
-
Out of the box support for cached resources
-
Out of the box support for type-casting data that comes in as parameter strings
-
More natural mapping of deserialised entities to existing classes
-
No communication via exceptions for http error status codes
-
Better extensibility - allows access to request/response objects, avoids class variables, favours symbols over strings etc.
-
Content Types in request headers
-
Consider support for OPTIONS and response codes 100/417
-
gems
-
json (json-jruby on JRuby)
-
active_support
-
ruby-libxml or Nokogiri (Wrest tries ruby-libxml first, then nokogiri, and will finally fall back on REXML; be aware that Wrest uses ActiveSupport::XmlMini, so if you’re using Wrest as a plugin in a Rails application, all xml parsing across the application will switch to using libxml if it’s available. You’re free to change this by hand by using the ActiveSupport::XmlMini.backend= method.)
-
multipart-post (needed only if multipart support is enabled)
-
rspec
-
rcov (unsupported on JRuby)
-
jeweler
Features that are planned, in progress or already implemented are documented in the CHANGELOG starting from version 0.0.8.
Wrest is released under the Apache 2.0 licence