I'm not a Django developer, but I think it'd be good to give your reasoning
for this, with examples. I'm so used to Django's routing I can't imagine
anything else.
On Friday, 18 July 2014 16:05:44 UTC+2, Cal Leeming [Simplicity Media Ltd]
wrote:
>
> Just had a look at django-nap, nice concept
Just had a look at django-nap, nice concept but it sadly seems to have
suffered the same over-engineering fate as the others (DRF, Piston,
Tastypie etc). Happy to discuss why in a separate thread, but probably
off topic for this one.
At present I'm just looking for proposals to introduce request
Sounds like you're heading for a cleaner version of the Publisher pattern
in django-nap...?
On 18 July 2014 07:34, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:
> Hello,
>
> Currently implementing a method dispatcher (e.g. a single URL that
> goes to
Hello,
Currently implementing a method dispatcher (e.g. a single URL that
goes to different views based on HTTP method) is not feasible because
it will break decorators.
For example:
https://djangosnippets.org/snippets/2041/
In theory you could use middleware to store the request object inside
