Rest-core 0.3.0 released

Ruby
1

rest-core https://github.com/cardinalblue/rest-core

by Cardinal Blue http://cardinalblue.com

DESCRIPTION:

A modular Ruby REST client collection/infrastructure

In this era of web services and mashups, we have seen a blooming of
REST
APIs. One might wonder, how do we use these APIs easily and elegantly?
Since REST is very simple compared to SOAP, it is not hard to build a
dedicated client ourselves.

We have developed rest-core with composable middlewares to build a
REST client, based on the effort from rest-graph. In the cases of
common APIs such as Facebook, Github, and Twitter, developers can
simply
use the built-in dedicated clients provided by rest-core, or do it
yourself
for any other REST APIs.

INSTALLATION:

gem install rest-core

Or if you want development version, put this in Gemfile:

gem 'rest-core', :git => 'git://github.com/cardinalblue/rest-

core.git’,
:submodules => true

CHANGES:

rest-core 0.3.0 – 2011-09-03

  • [facebook] RestGraph is Facebook now.

  • [facebook] Facebook::RailsUtil is imported from rest-graph

  • [facebook] Use json_decode instead of auto_decode as rest-graph

  • [facebook] No longer calls URI.encode on Facebook broken URL

  • [twitter] Fixed opts in Twitter#tweet

  • [twitter] Introduced Twitter::Error instead of RuntimeError!

  • [twitter] By default log nothing

  • rest-core We no longer explicitly depends on Rack

  • rest-core Added a shorthand RC to access RestCore

  • rest-core Eliminated a lot of warnings

  • [cache] All clients no longer have default hash cache

  • [oauth2_query] Now we always use the term “access_token”

  • [config] Now Config#load and Config#load_for_rails take namespace
    e.g. rest-core.yaml:

    development:
  facebook:
    app_id: 123
  twitter:
    consumer_key: abc