Hi,

Fair enough - you're free to discuss your ideas.

For this thread, I'd prefer sticking to ideas on whether to implement the HTTP methods in the urlresolver and if the idea is any good - how this could be done.

Right now the urlresolver works with strings or functions, not dictionaries. Adding dictionaries to the urlpatterns increases the complexity a bit and introduces a complete new concept & behaviour.

I'd prefer a simple solution that will allow you to specify the HTTP method for a view without adding noise to the whole urlresolver.

Any ideas?


Met vriendelijke groet,

Simon de Haan

Eight Media
+31 (0)26 38 42 440



On Sep 22, 2006, at 9:44 AM, limodou wrote:


On 9/22/06, Simon de Haan <[EMAIL PROTECTED]> wrote:
Hi Limodou,

Not sure about your decorator idea, personally I think it goes beyond the
scope of the url's in general and django's urlpatterns and is quite view
specific.

Any ideas about implementing the GET/POST/PUT/DELETE etc..?

Decorator is used for seperating some basic functionality, just like
user authentication, logging, etc. And for now, we should write them
in View code, so if the decorator is changed, so we need to modify
view code.

Yeah, this thread is talking about GET/POST/..., but I think it could
be extended for other things. If these things could be implemented,
and we might implmented an interface just like zope, and use it to
constrol the security ,authentication, logging, etc.

And these extend also include GET/POST/PUT/... etc.

If this idea is sound reasonable, so we can discuss more deeply, if
not, just skip it.

Why I think the urls.py is suit for these kind of things, because all
the methods can be exposed to user are saved in it. So we can make it
more strong and controllable I think.

-- 
I like python!


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---

Reply via email to