title: Asp.NET MVC is REST but Why Asp.NET WebForms are not?
body: <p>Okay I hear that thing all the time on internet when reading an article about MVC : "Since Asp.NET MVC is REST, it is easy to consume ... etc." I've never heard such a thing for Asp.NET Webforms and it makes me wonder what makes something REST.</p>
  
  <p>As I understood, REST means Representational State Transfer in which what a user see on their browser is a state. But I don't think it means it always should be like RPC as MVC does. It could be a physical page served by the server like how it works in Asp.NET WebForms (Default.aspx) As long as it returns a state representation, it is called REST.</p>
  
  <p>So if my understanding is fine, then shouldn't webforms be also REST?</p>
  
  <p>Uggh, I am kinda confused....</p>
  
  <p>Thanks in advance....</p>
  
  <p><strong>Edit and brief answer :</strong>
  Okay folks, listen up :) this is the answer I believe which is correct :</p>
  
  <p>As we know it REST should match basic principles below :</p>
  
  <pre><code>* Give every “thing” an ID
  * Link things together
  * Use standard methods
  * Resources with multiple representations
  * Communicate statelessly
  </code></pre>
  
  <p>So as we know it, webforms use highly postbacks, session to get idea about the previous requests and you can do postback countless times to get something like :</p>
  
  <p><code>search.aspx</code> and post the selected value of a <code>dropdownmenu</code> and there is no get, only post and postback from the server.</p>
  
  <p>Well it obviously cannot be restful architectural style.</p>