title: REST strategy for overloading GET verb
body: <p>Consider a need to create a GET endpoint for fetching Member details using either of 4 options (It's common in legacy application with RPC calls)</p>
  
  <ol>
  <li>Get member by ID </li>
  <li>Get member by SSN</li>
  <li>Get member by a combination of Phone and LastName (both must be passed)</li>
  </ol>
  
  <p>What's a recommended strategy to live the REST spirit and yet provide this flexibility?</p>
  
  <p>Some options I could think of are:</p>
  
  <p><strong>Parameters Based</strong></p>
  
  <pre><code>/user/{ID}  
  /user?ssn=?
  /user?phone=?&amp;lname=?
  </code></pre>
  
  <p><strong>Separate Endpoints</strong></p>
  
  <pre><code>/user/{ID}
  /user/SSN/{SSNID}
  /user/{lname}/{phone}
  </code></pre>
  
  <p><strong>RPC for custom</strong></p>
  
  <pre><code>/user/{ID}
  /user/findBySSN/
  /user/findbycontact/
  </code></pre>