Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Assuming you get to decide what <em>kind</em> of Web Service you want, and a RESTful XML Web Service is an acceptable choice, then Rails applications practically do this by default. When you generate scaffolding code, your controller will actually be ready to interface with as a RESTful Web Service.</p> <p>Of course, that's not everything you need to know and do, but the subject seems to be covered very well by the following series of articles...</p> <ol> <li><a href="http://css.dzone.com/news/rest-with-rails-part-1" rel="nofollow">http://css.dzone.com/news/rest-with-rails-part-1</a></li> <li><a href="http://css.dzone.com/news/rest-with-rails-part-2-serving" rel="nofollow">http://css.dzone.com/news/rest-with-rails-part-2-serving</a></li> <li><a href="http://css.dzone.com/news/rest-with-rails-part-iii-using" rel="nofollow">http://css.dzone.com/news/rest-with-rails-part-iii-using</a></li> </ol> <p>Unfortunately, there seem to be some JavaScript errors on those pages, but they're still usable.</p> <p>I know this doesn't answer the OAuth part of your question, but this article ( <a href="http://stakeventures.com/articles/2009/07/21/consuming-oauth-intelligently-in-rails" rel="nofollow">http://stakeventures.com/articles/2009/07/21/consuming-oauth-intelligently-in-rails</a> ) apears to have some useful information on that subject. Note that the info here is slightly out of date if you'll be using Rails 3 because you'll want to list the gems in your Gemfile and run <code>bundle install</code> rather than adding <code>config.gem ...</code> lines to your environment.rb file.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload