On Fri, 22 Jun 2007, Raymond Wan wrote:
> Ah! That's how you maintain variables (or state) from one request to
> another...via a database. And then it's fine to store a username, or
> better yet, a session id as a cookie on the client side to act as a key
> to look-up into the database. There no other way for this information
> (or any variable, for that matter) to persist across requests by the
> same user other than keeping some kind of information on the client
> side? (Other than URLs.)
>
> I see, thanks! I was thinking of global variables or even <%init>
> blocks to set and store variables, but each request (even within a
> single persistent connection by the same client) is independent and no
> variable can exist across requests?
What if the persistent connection were from a proxy with different
users?
(I have no idea whether that's possible, but unless you're sure it
isn't, I'm sure you can see the problems with assuming that it isn't).
:)
---------------------------------------------------------------------
| Name: Tim Nelson | Because the Creator is, |
| E-mail: [EMAIL PROTECTED] | I am |
---------------------------------------------------------------------
----BEGIN GEEK CODE BLOCK----
Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V-
PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI++++ D G+ e++>++++ h! y-
-----END GEEK CODE BLOCK-----
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
