Invest heavily in a FAST database for storing session ID's (i.e. really good indexing routines), one that can hold a lot of session variables and access them quickly. You will be keeping them around for a LONG time. Neat approach; I like the concept.
Test your session table with millions of rows. If you plan to have the site persist for years, you will need to have some sort of "last visited" date stamp so you can kill off sessions that are over X months old (i.e. they aren't coming back).
Accessing the site from public terminals will create a problem in that subsequent users will not see "old" data. That may or may not be a concern to you. Consider a "new visitors click here" thing to allow them to reset what the system considers new for that browser.
You also need a really good hash algorithm to generate unique session tokens because you don't want them to repeat by mistake.
In reply to Re: combining cookies and user registration - strategies?
by Cabrion
in thread combining cookies and user registration - strategies?
by Hagbone
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |