title: Versioning a TastyPie Api with the Accept header
body: <p>I'm not trying to start a religious war, but I <em>personally</em> really don't like api version information in the URL of a resource.  I think the best way to do it is via the Accept header of the resource or adding a ?version=2 to the query string.  If you are curious about this topic.  There are a number of good (an passionate) posts on StackOverflow on the topic.  Here is a good <a href="https://stackoverflow.com/questions/389169/best-practices-for-api-versioning">thread here</a>.  Also, IMHO, a good blog post <a href="http://blog.steveklabnik.com/posts/2011-07-03-nobody-understands-rest-or-http" rel="nofollow noreferrer">here</a> by Steve Klabnik.  Again, these are just my perferences, and I'm not trying to create a thread on this topic (again).</p>
  
  <p>I'm currently looking for a Django package to help with creating a RESTful API.  After some reading, it seems like TastyPie has most of what I want/need and is well supported (and has really good docs).  And I'm just wondering if there is a way to implement a different versioning scheme?  Has anyone else out there done this?  Is there another package that might work more the way I want?</p>