Configurable request parsing.

[Tom Christie]

This ticket if for implementing a request parsing API that ensures the Request objects can nicely handle JSON and other submitted types in addition the the existing multipart parsing.

The proposed API is based on this discussion: ​https://groups.google.com/forum/#!searchin/django-developers/request.DATA/django-developers/s8OZ9yNh-8c/oCbNL5x6avAJ

• request.DATA or request.data for accessing the parsed data.
• request.parsers or similar for modifying the parsers prior to parsing on a per-view basis.
• request.accepted_parser or similar for branching on media type if needed.
• A setting REQUEST_PARSERS or similar, that controls the default set of installed parsers.

[Asif Saifuddin Auvi]

​https://github.com/django/deps/blob/master/draft/content-negotiation.rst

reading the DEP

my thoughts are wouldn't it better/nicer to handle the content negotiation per view based content negotiation? and there should be decorators to handle content negotiation in view level?

+ is it really necessary to introduce new global settings?

[Asif Saifuddin Auvi]

or this is the HTTP Handling part only? view parts will be implemented differently in another ticket? serialization in another part? hope you don't get me wrong for asking too many questions.