Re: Awkwardness of overriding View.dispatch for method-agnostic request-handling

2012-04-11 Thread Meshy
I agree that there is a need for this -- it has come up several times for me now -- however, I prefer my proposal (pretty printed here: https://gist.github.com/1957251 , code below...) mentioned in the topic "Class based views: A standard hook for http-method-independent code" (https://groups.g

Re: Awkwardness of overriding View.dispatch for method-agnostic request-handling

2012-04-10 Thread schinckel
I agree: but this means that the actual dispatcher (that, according to the comments, "dispatch[es] to the right method", is called handle(), rather than dispatch. Perhaps the assignation of request/args/kwargs could happen before dispatch is called? -- You received this message because you a

Awkwardness of overriding View.dispatch for method-agnostic request-handling

2012-04-10 Thread Alexander Dutton
Hi all, [I think this has been mentioned on django-developers before, but I can't find it. If this would be better as an RFE in a ticket, shout at me and I'll raise it there.] In a couple of our projects we have various views on resources differentiated by some aspect of the request (query parame