TheCloneArmy/RestApiGuide
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added previous/next links to lessons pages.

Browse Source
This commit is contained in:
Todd Fredrich
2012-06-18 11:41:27 -06:00
parent c4cc30f78c
commit 559a3ece51
4 changed files with 33 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
lessons/httpmethods.html
View File

@ -36,13 +36,23 @@
<body>
<div class="container">
<div class="row">
<div class="span12">
<div class="span8">
<h1>Using HTTP Methods for RESTful Services</h1>
<p>The HTTP verbs comprise a major portion of our “uniform interface” constraint and provide us the action counterpart to the noun-based resource. The primary or most-commonly-used HTTP verbs (or methods, as they are properly called) are POST, GET, PUT, and DELETE. These correspond to create, read, update, and delete (or CRUD) operations, respectively. There are a number of other verbs, too, but are utilized less frequently. Of those less-frequent methods, OPTIONS and HEAD are used more often than others.</p>
</div>
<div class="span4">
<ul class="pager">
<li>
<a href="restquicktips.html"><i class="icon-step-backward"></i> Previous</a>
</li>
<li>
<a href="../httpstatuscodes.html">Next <i class="icon-step-forward"></i></a>
</li>
</ul>
</div>
</div>
<div class="row">
<div class="span12">
<p>The HTTP verbs comprise a major portion of our “uniform interface” constraint and provide us the action counterpart to the noun-based resource. The primary or most-commonly-used HTTP verbs (or methods, as they are properly called) are POST, GET, PUT, and DELETE. These correspond to create, read, update, and delete (or CRUD) operations, respectively. There are a number of other verbs, too, but are utilized less frequently. Of those less-frequent methods, OPTIONS and HEAD are used more often than others.</p>
<p>Below is a table summarizing recommended return values of the primary HTTP methods in combination with the resource URIs:</p>
<table class="table table-striped table-bordered">
<thead>

16
lessons/restquicktips.html
View File

@ -36,8 +36,22 @@
<body>
<div class="container">
<div class="row">
<div class="span12">
<div class="span8">
<h1>REST API Quick Tips</h1>
</div>
<div class="span4">
<ul class="pager">
<li>
<a href="whatisrest.html"><i class="icon-step-backward"></i> Previous</a>
</li>
<li>
<a href="httpmethods.html">Next <i class="icon-step-forward"></i></a>
</li>
</ul>
</div>
</div>
<div class="row">
<div class="span12">
<p>Whether it's technically RESTful or not (according to the six constraints mentioned above), here are a few recommended REST-like concepts that will result in better, more usable services:</p>
<h2>Use HTTP Verbs to Mean Something</h2>
<p>Any API consumer is capable of sending GET, POST, PUT, and DELETE verbs, and they greatly enhance the clarity of what a given request does. Also, GET requests must not change any underlying resource data. Measurements and tracking may still occur, which updates data, but not resource data identified by the URI.</p>

8
lessons/whatisrest.html
View File

@ -36,16 +36,16 @@
<body>
<div class="container">
<div class="row">
<div class="span10">
<div class="span8">
<h1>What Is REST?</h1>
</div>
<div class="span2">
<div class="span4">
<ul class="pager">
<li>
<a href="#">Previous</a>
<a href="../index.html"><i class="icon-step-backward"></i> Previous</a>
</li>
<li>
<a href="#">Next</a>
<a href="restquicktips.html">Next <i class="icon-step-forward"></i></a>
</li>
</ul>
</div>