title: In a web service application, is verb-orientation still useful?
body: <p>Thanks for looking!</p>
  <h2>Background</h2>
  <p>I am building a strictly machine-to-machine web-service (restful) application.  The application will listen for requests, retrieve data, construct objects, serialize to JSON and return the JSON object.</p>
  <p>This application will ultimately be used by other web applications as well as iOS apps, Android apps, and even desktop apps.</p>
  <p>The existing code that I have inherited makes a distinction based on <em>how</em> the service was called in terms of HTTP verbs (GET, POST, etc).</p>
  <h2>Question</h2>
  <p>In this day and age of machine-to-machine communication, is the HTTP verb even relevant any longer?  Could it in fact be constraining for future adoption of the service API to base the code around HTTP verbs?</p>
  <h2>Update</h2>
  <p><code>fmgp</code> provides a clear answer to &quot;why&quot; these verbs are used, but I feel should I clarify my concern:</p>
  <p>Will other platforms such as iOS or Android (for example) be able to originate HTTP verb-based calls like <code>GET</code> and <code>POST</code>?  If the answer is &quot;no&quot; then I assume that we should stay away from relying on these verbs and instead build the desired action into the request URL as a parameter.</p>