Django Content Negotiation implement

[Asif Saifuddin]

Hi,
 when https://github.com/django/deps/blob/master/drafts/content-negotiation.rst this dep is to be implemented in django? 1.8?

Regards

Asif

[Florian Apolloner]

Whenever it is done, I am not aware of anyone working on it.

[Tom Christie]

There's no particular timeline for it. The two people most likely to progress it are Mark Lavin and myself.

Mark is the author of the DEP and has been busy lately, focusing on releasing the "Lightweight Django" book that he's co-authored. He has mentioned that it's possible he'll get back to progressing the DEP following on from that.

My priority at the moment is the REST framework kickstarter, perhaps I'd get onto the DEP after that, tho as things currently stand I'd prefer if someone else was going to be primarily responsible and for me to just help with design guidance.

Anyone else is also free to get the ball rolling on it - we've got a very clear idea what we need, so it just needs someone to make the commitment to it, in which case I'd be very willing to also put some time into guiding it through.

Hope that helps answer your question. Contributions are of course very welcome,

All the best,

Tom

[Asif Saifuddin]

Thank you both for your kind response.

I have only almost about a year working with django and still learing. My django and python skills are still so limited as far I know. Reading the dep and other related links of discussions and browsing some source code things are bit overwhelming to me right now :p  but I am willing to expand my technical knowledge  by learning and trying to contribute on this part.

I have some limitations in design decisions and understanding the overall implementation process But still I want to start working on this part primarily with you guys helps and suggestions.

I'll be trying to enhance my knowledge base about django request response and other related stuffs necessary if you please show me some light to get started or from where actually should I start.

Kind Regards

Asif 

[Asif Saifuddin]

Thank you both for your kind response.

I have only almost about a year working with django and still learing. My django and python skills are still so limited as far I know. Reading the dep and other related links of discussions and browsing some source code things are bit overwhelming to me right now :p  but I am willing to expand my technical knowledge  by learning and trying to contribute on this part.

I have some limitations in design decisions and understanding the overall implementation process But still I want to start working on this part primarily with you guys helps and suggestions.

I'll be trying to enhance my knowledge base about django request response and other related stuffs necessary if you please show me some light to get started or from where actually should I start.

Kind Regards

Asif 

--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/g1P7H1PhZaY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/436d3c71-2567-462d-a035-9880511124ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tom Christie]

> I'll be trying to enhance my knowledge base about django request response and other related stuffs necessary if you please show me some light to get started or from where actually should I start.

I'd generally think that a decent place to start would be to write up what some of the documentation *before* actually implementing any code.

Figure out where would you describe `request.data` in the Django docs, figure out what other bits of the DEP would need to be public documented API, ignoring the under-the-hood implementation details what does the user need to know about them and how they work?

An alternative way to get involved without necessarily diving right into the DEP might be to review any outstanding tickets to do with HTTP handling and requests and responses. Even if you don't feel able to resolve any of those issues having a browse through and trying to understand them would be a good way to start getting to grips with the Django codebase.

Hope that helps,

  Tom

[Mark Lavin]

Hi,

Tom has done a great job describing why this has stalled recently. I plan to pick back up on this now that the book has been released. I agree that defining the public API is the best first step and the current DEP is not sufficient in this regard. Before making any internal changes we need to define how the user will define new content types: where and at what level. We also need to define how the user will describe multiple response types for a view.

At a code level it's worth digging into how the current form-encoded and multi-part data is detected and parsed in Django. It's also worth reviewing how this problem has been solved by the community before: django-piston, django-tasypie, django-rest-framework, django-nap, restless, etc to look for common patterns and solutions as well as things that haven't worked well in hindsight.

Best,

Mark