I posted this yesterday:

> Specifically, I'm considering using hidden fields for persistent object
> properties because (1) I don't want cookies to be an issue, (2) I prefer not
> to have session IDs appear in a URL, and (3) I prefer not to use require a
> database just to store persistent properties.

After Justin and Ernest straightened me out, I went back to the drawing
board and came up with a method that I call Invisible GET.

Let's say my page is at <http://www.getsome.com/>.  When I want to change
the month (for example), I...

    (1)  Open <http://www.getsome.com/submit.php?month=3&;

    (2)  In submit.php script, I throw all $_REQUEST variables (except
         "target" and "PHPSESSID") into $_SESSION variables, and...

    (3)  ...redirect to $_REQUEST['target'] via header().

I've sure I've invented something that nobody's done before.   :^P
This method feels about perfect.  Users won't be seeing or bookmarking
garbage-filled URLs, and I'm not using lots of hacky stuff to achieve it.

I wish I could generate submit.php on the fly, though -- I'm trying very
hard not to pollute the web folder with anything that I don't have to, and
file creation/deletion is very expensive since I have to do it via FTP.  Any
ideas on this one?

-- Charles Wiltgen

PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to