Same function used for GET and POST

[aaronsw]

Django encourages the use of the same function for both GET and POST (not to mention DELETE) methods. For example, 'module.method' resolves to:

def method(request): ...

In the web app framework I wrote, it resolves to:

class method:
    def GET(self, request): ...
    def POST(self, request): ...
    ...

This ensures that POST functions don't accidentally leak into GETs. If both POST and GET want to reuse code, then they can add a new method to the class. This also allows this style:

...
(r'^/method/(.*)', 'module.method')
...

class method:
    GET = web.autodelegate("GET_")
    POST = web.autodelegate("POST_")
    
    def GET_(self, request): ... # index
    def GET_pagename(self, request): ...
    def POST_pagename(self, request): ...

which makes adding new URLs easy. The code for autodelegate is simply:

def autodelegate(prefix=''):
    def internal(self, request, arg):
        func = prefix+arg
        if hasattr(self, func): return getattr(self, func)(request)
        else: raise NotFound
    return internal

[Jacob]

FYI, there are decorators in django.views.decorators.http to control which request methods a given view allows; this is a very interesting idea, though.

[brantley (deadwisdom@…]

This is an interesting idea. But you could still do this sort of thing, actually without changes in django. If you had your method class define call(), like so:

class MethodPage:
   def __call__(request, **kw):
      if request.GET:
          self.get(request, **kw)
      elif request.POST:
          self.post(request, **kw)
      else:
          self.default(request, **kw)

   def get(request, **kw):
      pass
   def post(request, **kw):
      pass
   def default(request, **kw):
      pass

And then use it in your page:

class method(MethodPage):
    def get(request, arg1, arg2):
        "Does stuff on get."
    def post(request, arg1, arg2):
        "Does stuff on post."

[anonymous]

Oh, and finally, make it a singleton:

    method = method()

[hugo]

Actually your code only works if you make get/post/whatever classmethods, as otherwise they will require a MethodPage object in the first parameter ;)

[Adrian Holovaty]

See the comments on this ticket.

[Adrian Holovaty]

Milestone Version 0.91 deleted