Someone remind me never to post to list before I've had my second coffee? :)
Of course the above would trivially be handled using middleware. -- C On 4 September 2013 10:05, Curtis Maloney <[email protected]>wrote: > What do people think of an extensible registration approach to handling > request content types? > > Something along the lines of ('POST', [list of content types], class to > handle it) > > This would mean adding a request.JSON would be simple for the projects > that want it, and even overriding how the existing content types are > handled would be possible. [I haven't seen a use case for such yet, but > it's a wild world out there :)] > > -- > Curtis > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
