title: what is rest,and what is its advantage
body: <p>I have googled about the docs of rest, but I am not exactly sure I understand it.</p>
  
  <p>What I can see in rest is that its URL is clean, for example:</p>
  
  <pre><code>http://host/webservice.asmx?name=xname&amp;type=xtype
  </code></pre>
  
  <p>If in REST style, it is perhaps:</p>
  
  <pre><code>http://host/webservice.asmx/xname/xtype
  </code></pre>
  
  <p>Isn't it?</p>
  
  <p>So I just found the URL is cleaner, but I can not find any other advantages.</p>
  
  <p>Can anyone tell me more?</p>
  
  <p>I have some more questions:</p>
  
  <ol>
  <li><p>I found that some application built on Ruby-on-Rails all use the clean URL, for example:</p>
  
  <p><a href="http://xxx/blog/list" rel="nofollow">http://xxx/blog/list</a></p>
  
  <p><a href="http://xxx/blog/edit/1" rel="nofollow">http://xxx/blog/edit/1</a></p>
  
  <p><a href="http://xxx/blog/1" rel="nofollow">http://xxx/blog/1</a></p>
  
  <p>So is there any relationship between them?</p></li>
  <li><p>URL rewriting</p>
  
  <p>Is URL rewriting one of the ways to implement REST?</p></li>
  <li><p>We have some web service built on ASP.NET, are there any ways to change that to a REST architecture?</p></li>
  </ol>
  
  <p><hr/><hr/>
  <strong>UPDATE:</strong></p>
  
  <p>I have read this article(rest-to-my-wife),it seems that using the verbs provided by http(post/get/put/delete) we can do different operation to a resource using the same url just put the realated data in the http body;
  for example,I want to create a new order:</p>
  
  <pre><code>POST http://www.store.com/order，
  &lt;purchase-order&gt;
    &lt;item&gt; ... &lt;/item&gt;
  &lt;/purchase-order&gt;
  </code></pre>
  
  <p>But I still have some questions:</p>
  
  <p><strong>1) how we set the http body in the page?</strong></p>
  
  <p>ANother example,I want to delete an order:</p>
  
  <p>Delete <a href="http://www.store.com/order/1" rel="nofollow">http://www.store.com/order/1</a></p>
  
  <p>But in the page,the url is just a link,</p>
  
  <p>Mabye it is like this:</p>
  
  <p><a href="http://www.store.com/order/1" rel="nofollow">delete this order</a></p>
  
  <p>it is static,how can we tell the browser that when it send this url to the server,it should use the "delete" manner rather than "get"?</p>
  
  <p><strong>2) is it will cause the extra work in server side?</strong></p>
  
  <p>Since we may send the same url with different http method(get/post...) to the server,so the server may have to parse the http header and body to make sure what operation the user want to do for this url(maybe using the 'resource' instead of 'url' is better,but I can not tell the difference between  url and uri and resouce)?</p>
  
  <p>Take the same url for example:</p>
  
  <pre><code>http://www.store.com/order/1
  </code></pre>
  
  <p>If the server find that the http method is "get",he may know that "oh,this guy just want to get the info of the order whose id is 1",if the method is "delete",he know "oh,this guy want to delete the order whose id is 1".</p>
  
  <p>So it seems that this manner will transfer the extra work from client side to server side.</p>
  
  <p>Which I mean that in the client the url is all the same,it is easier,but for the server side it need more work,is this true?</p>