if you need access to your session among different servers,
it's the best way to store session data inside a database,
so every server can access it easily. The file container
is accessible only for local users on the server, at least
when you set up normal server configuration and not
some nasty stuff with servers shareing hdds or
partitions or something. There's no other difference
between the file container and the database container.
Perhaps the database driven container is running a bit slower,
for you have to connect to the database, and that costs
some time, at least if you don't use persistent connections.
Persistent connections are only possible if you're running PHP
as Apache Module, not in CGI version.
So it's up to you to decide what you need.
Regards Michael
Vins [EMAIL PROTECTED] schrieb im Newsbeitrag
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
For example:
one form...
- First name
- last name
- address
- country
- phone
- email
- mobile number
After you click submit on the first page, it sends you to a preview data
page where you can check all the data.
instead of inserting tons of hidden input form fields and waist download
time, use a session.
after the button on the preview page is clicked, submit to a save page,
where data will be entered into a db
but all values my be called from the session.
now would it be wise, faster and more safer to use a database or a file to
save the sessions ?
Vins [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Session Data.
What is the best.
to save in database, or to save as file ???
let me know.
Cheerz
Vins
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
