title: AFNetworking - Request method as a parameter
body: <p>I'm seeing in <a href="http://afnetworking.github.io/AFNetworking/Classes/AFHTTPClient.html#tasks" rel="nofollow">AFHTTPClient documentation</a> these pretty tasks for <em>Making HTTP Requests</em>:</p>
  
  <pre><code>- getPath:parameters:success:failure:
  - postPath:parameters:success:failure:
  - putPath:parameters:success:failure:
  - deletePath:parameters:success:failure:
  - patchPath:parameters:success:failure:
  </code></pre>
  
  <p>Now if I need update or create something on my server,<br>
  let's say I want to differentiate the update/create by the method:</p>
  
  <ul>
  <li>create -> PUT</li>
  <li>update -> POST</li>
  </ul>
  
  <p>Would there be a way to specify the method as a parameter somewhere, like:</p>
  
  <pre><code>- requestPath:method:parameters:success:failure:
  </code></pre>
  
  <p>Obviously I can create my own dispatcher, but the question is more about why this seems to be done intentionnaly as it is (hoping I'm clear).</p>