[Tutor] Design suggestion - is a cookie the answer?
dyoo at hkn.eecs.berkeley.edu
Tue Jan 17 02:34:32 CET 2006
> On 16/01/06, Alan Gauld <alan.gauld at freenet.co.uk> wrote:
> > explicit events you register with it(*). One of the problems of using
> > CGI is the ese of frigging it. I assume you are using GET instead of
> > POST? GET is the default submission method but POST is nearly always
> > better and should avoid the problem here. (I think, I haven't tried
> > it!)
> I believe the python CGI module is submission-method agnostic --- your
> code doesn't need to know or care whether the data was submitted using
> POST or GET. So, even if you are using POST, clever kids could, I
> think, construct a GET url to do the same thing.
Sorry I missed most of this thread! I wanted to interject that there are
some experimental web frameworks that might allow us to get around the
issues with browser reload. Most of these fall under "continuation-based"
web frameworks. For example, CherryFlow:
There are links on that page that talk about this in more detail.
However, I have to admit that the only continuation web frameworks I've
been playing with have been in PLT Scheme, so I'm not so sure how mature
the Python implementations are.
Best of wishes!
More information about the Tutor