fluffymike at googlemail.com
Wed Mar 5 06:47:51 EST 2008
I've just come back to this thread as I'm just about to alter the
session handling in tha app that I'm working on. It currently uses
the url method, which I plan to replace.
I'm struggling to accept the form method, because as you say no more
Now I like the old links, so cookies seems like a no brainer to me.
Can anyone explain why the form method is better and how you implement
Developer - BookBank.com
On 08/02/2008, Michael Peters <mpeters at plusthree.com> wrote:
> Stephen Carville wrote:
> > Seems to me it makes more sense to embed the session ID or any other
> > tracking as hidden variables in a form and send it back as a POST.
> This assumes then that every request you make is now a post request. Which means
> not more <a> links, just forms. And this also breaks REST style apps (and really
> anything that tries to have meaningful HTTP semantics) since POST requests are
> for things that could change the data server-side and GET requests are for
> anything that won't (idempotent). In this day and age you really have to expect
> long term, but why should anyone object to memory-only cookies?
> Michael Peters
> Plus Three, LP
More information about the cgiapp