Adam's right, "POST = GET" should work fine.
As for the "whether or not to do it" debate, I wrote a blog entry asking
that question some time ago, and discovered many reasons not to do it, and a
few reasons you might want to do it (see the comments):
http://blog.micropledge.com/2007/06/get-to-do-posts-job/
It was interesting to note that Paul Buchheit (one of the creators of Gmail)
is pretty pragmatic on the issue:
http://paulbuchheit.blogspot.com/2007/06/dogmatic-programmer-when-software.html
-Ben
On Jan 26, 2008 10:40 AM, Adam Atlas <[EMAIL PROTECTED]> wrote:
>
>
> On 25 Jan 2008, at 16:38, [EMAIL PROTECTED] wrote:
> > how do i create a class that has same definitions for both GET and
> > POST?
>
> class blah:
> def GET(self):
> ...
> POST = GET
>
> I think that would work.
>
> >
>
--
Ben Hoyt, http://benhoyt.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web.py" 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/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---
