Persistent in the case of globals in Rivet means that, in one particular
child process, a variable will not be deleted between requests. Since
it's tied to a system process and not a user, it's not useful for user
information. On the other hand, it is useful for things like database
handles - you can define a proc to check if it exists, create it if it
doesn't, and return it in either case.
ok, I'm going to expose my vast ignorance in web programming: what
do you mean for 'request' in this context? Apache child processes
have no knowledge of concepts as 'session', so when the link
(and the 'request' context) between client and server's child
process is dropped?
A request is one client to server round trip. For example:
GET /index.rvt HTTP/1.0
That asks for just that one page, no pictures, nothing else - all that
is fetched separately.
This looks like an ok description, and has some promising links.
http://en.wikipedia.org/wiki/HTTP
In any case, that's correct, there is no state unless you create it
artificially, by using the session package for instance.
--
David N. Welton
- http://www.dedasys.com/davidw/
Linux, Open Source Consulting
- http://www.dedasys.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
