Another thing to consider, most users on the internet allow cookies, and
those that don't want cookies can usually differentiate between allowing
session cookies and other types of cookies.

In the end, if a user doesn't want to allow cookies, they shouldn't expect
to be able to do e-commerce type stuff like purchasing items, or even have
user accounts.

Considering they don't allow cookies, these same users probably don't want
to sign up and give you their information anyways.

Use sessions, that is what they are there for.

Jason Lotito - PHP Developer's Network

----- Original Message -----
From: "Thomas Deliduka" <[EMAIL PROTECTED]>
Sent: Thursday, April 04, 2002 4:54 PM
Subject: Re: [PHP] Reliability of sessions

> On 4/4/02 4:46 PM this was written:
> > I am not sure about the reliability of sessions, but the way I do it is
> > also through several processes, and the information passed via <input
> > type=hidden name=name value=$name> I can demonstrate it if you want.
> That's what I was wanting to avoid. That's a lot of hidden fields. Not to
> mention if you  have to add to the first step, you need to modify all the
> others.
> > Even though sessions are more handy, I still don't know what happens if
> > cookies are disabled in the client's browser.
> I pass the session ID in the URL on every page so whether or not cookies
> set, the session stays intact.
> I'm thinking that I solved my old problem and I'm going to do it in the
> database and pass the order number. That's probably the best way. I only
> have to provide for order clean-up for those that started the process and
> decided not to check out.
> --
> Thomas Deliduka
> IT Manager
>      -------------------------
> New Eve Media
> The Solution To Your Internet Angst
> --
> PHP General Mailing List (
> To unsubscribe, visit:

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to