You need some way to identify users, particularly if you are going to maintain their state information in the database. Cookies are one of the best options, because they are easy, work well and fairly universal. But what happens when two users use the same computer (eg at an internet cafe)?

Without cookies and without a login, I can't see how you can maintain state outside of the current session. By only keeping the session id in the URL, you can't reliably identify a user returning to the site.

Ari Maniatis


On Wednesday, May 21, 2003, at 04:28 AM, Brad Perkins wrote:

I suppose I could update a "last_interaction_timestamp" cookie and examine this when a new session is created, but I don't want to have to rely on cookies being on.
Also in the system in question users will be anonymous (no login required) so I can't think of a reliable way to store this information in the database.





--------------------------> ish group pty ltd 7 Darghan St Glebe 2037 Australia phone +61 2 9660 1400 fax +61 2 9660 7400 http www.ish.com.au | email [EMAIL PROTECTED] PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8



Reply via email to