aboutsummaryrefslogtreecommitdiffstats
path: root/activeresource/README.rdoc
diff options
context:
space:
mode:
authorOlli Jokinen <olli.jokinen@enemy.fi>2011-12-01 15:32:59 +0200
committerOlli Jokinen <olli.jokinen@enemy.fi>2011-12-01 15:32:59 +0200
commitb4e1903d23a760028d58bc3bb20a1d491bfd4a4b (patch)
treea40bdce1bd4800124ab6eaed2a6be017bf9cfd3d /activeresource/README.rdoc
parentfae9ad9c712decef70b379f5aa1faa0149902831 (diff)
parent1e51cd957e3c90f4be35f1f0c4c380d8f7d40d66 (diff)
downloadrails-b4e1903d23a760028d58bc3bb20a1d491bfd4a4b.tar.gz
rails-b4e1903d23a760028d58bc3bb20a1d491bfd4a4b.tar.bz2
rails-b4e1903d23a760028d58bc3bb20a1d491bfd4a4b.zip
Merge remote-tracking branch 'upstream/master'
Diffstat (limited to 'activeresource/README.rdoc')
-rw-r--r--activeresource/README.rdoc10
1 files changed, 5 insertions, 5 deletions
diff --git a/activeresource/README.rdoc b/activeresource/README.rdoc
index b03e8c4c25..c86289c5fe 100644
--- a/activeresource/README.rdoc
+++ b/activeresource/README.rdoc
@@ -22,13 +22,13 @@ received and serialized into a usable Ruby object.
== Download and installation
-The latest version of Active Support can be installed with Rubygems:
+The latest version of Active Support can be installed with RubyGems:
% [sudo] gem install activeresource
Source code can be downloaded as part of the Rails project on GitHub
-* https://github.com/rails/rails/tree/master/activeresource/
+* https://github.com/rails/rails/tree/master/activeresource
=== Configuration and Usage
@@ -36,7 +36,7 @@ Putting Active Resource to use is very similar to Active Record. It's as simple
that inherits from ActiveResource::Base and providing a <tt>site</tt> class variable to it:
class Person < ActiveResource::Base
- self.site = "http://api.people.com:3000/"
+ self.site = "http://api.people.com:3000"
end
Now the Person class is REST enabled and can invoke REST services very similarly to how Active Record invokes
@@ -135,8 +135,8 @@ as the id of the ARes object.
==== Update
-'save' is also used to update an existing resource - and follows the same protocol as creating a resource
-with the exception that no response headers are needed - just an empty response when the update on the
+'save' is also used to update an existing resource and follows the same protocol as creating a resource
+with the exception that no response headers are needed -- just an empty response when the update on the
server side was successful.
# <person><first>Ryan</first></person>