On Mon, 2002-08-12 at 12:29, Doug Schasteen wrote:
Ok. I'm not sure exactly how to respond to this, but I'll try. Pretty
much any web server running new applications will "require" persistence.
I'm actually not a unix admin by trade, I'm a php programmer, so this is
one area where I actually know what I'm talking about. Not everything on
a web site uses server side sessions, but some things do. Some things
need to. In fact, you'd have to be running a very basic static-content
website to not need to use server-side sessions and cookies. I remember
back in the day when I used to "log in" people to my website by storing
their IP in a database. I remember how many problems that caused because
of NAT in other people's offices. Now that I can use php server-side
sessions, that is no longer a problem. So I guess my point is that by
saying that persistence is unnecessary, you are also saying that
sessions are unnecessary, which is not true.
Simple, Save your PHP session information on the server in either a
shared directory or in a MySQL database. The sessions exists across
several servers and persistance is not needed.
Isn't there a setting in php.ini to save server sessions to a file.
Ours is set to /shared/tmp which is NFS mounted on all the servers. PHP
should also not return the session cookie to the client until the
session info is on disk.
Persistance has its use but many times it is used to correct for lazy
programing style.
-Matt
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
