From a5a98b51dfc41dea543aef828c129ff6c51f3347 Mon Sep 17 00:00:00 2001 From: Julien Kirch Date: Mon, 1 Feb 2010 18:12:21 +0100 Subject: [PATCH] Updated README to match with Response refactoring --- README.rdoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.rdoc b/README.rdoc index fb3f1a9..e9cb4d6 100644 --- a/README.rdoc +++ b/README.rdoc @@ -63,7 +63,7 @@ See RestClient::Resource docs for details. rescue => e e.response end - ➔ "\n\n404 Not Found..." + ➔ 404 Resource Not Found | text/html 282 bytes == Result handling @@ -72,7 +72,7 @@ Response.return! can be called to invoke the default response's behavior (return # Don't raise exceptions but return the response RestClient.get('http://example.com/resource'){|response| response} - ➔ "\n\n404 Not Found..." + ➔ 404 Resource Not Found | text/html 282 bytes # Manage a specific error code RestClient.get('http://my-rest-service.com/resource'){ |response| @@ -103,17 +103,17 @@ For cases not covered by the general API, you can use the RestClient::Resource c The restclient shell command gives an IRB session with RestClient already loaded: $ restclient - ➔ RestClient.get 'http://example.com' + >> RestClient.get 'http://example.com' Specify a URL argument for get/post/put/delete on that resource: $ restclient http://example.com - ➔ put '/resource', 'data' + >> put '/resource', 'data' Add a user and password for authenticated resources: $ restclient https://example.com user pass - ➔ delete '/private/resource' + >> delete '/private/resource' Create ~/.restclient for named sessions: