title: Designing URLs with MVC
body: <p>Say I have a list of orders I want to display.  I want to give the user the ability to show all orders, all orders from a certain state, and all orders from a certain category.  Each of these can be filtered by a date range.</p>
  
  <p>Without worrying about routing, I might just add each on the query string:</p>
  
  <pre><code>/orders?State=TX&amp;Category=Books&amp;DateRange=Yesterday
  </code></pre>
  
  <p>While I could easily make this work, it doesn't "feel" like this is the correct MVC-way of doing things.</p>
  
  <p>I could have routes that look something like this:</p>
  
  <pre><code>/orders/              
  /orders/state/{state}
  /orders/category/{category}
  /orders/state/{state}/category/{category}/
  /orders/state/{state}/category/{category}/Date/{date-range}
  </code></pre>
  
  <p>But I'd still want to support each of those filters not being there.  Is there a better way of handling this or am I just over thinking the whole thing?  </p>
  
  <p>If I go the URL only path, it isn't clear how I would create these routes without just repeating them for all the combinations I would want (state, no category, date, state, no category, no date, no state, category, date, etc.)</p>