>> On server create a mysql table where you generate unique IDs for each >> visitor and assign information to that ID in another table.
> Why two tables? I was planning to use just one. Normally you have one table with an ID and some info which normally never changes per visit like IP, browser agend, login information and such. If the user visits x pages, what do you want to do? A textblob where you record the pages visited? Would be a mess. What if you want to answer this question? "How many times has a user visited this page in the last week?" or "Has he visited this page?" or "Who might be interested in this? (Look who has visited some pages which match)" Most programmers would use something like this: create table cookie2id ( id primary key browseragend ip loginuser loginpass lastlogin ) create table usertracking ( cookie2id_id primary id visitedon url referer ) > Again, I have never used cookies before, so I need to ask, why "write > nothing else"? Users can not look into server data if you do allow them - but users can look into cookies. They get easily scared if they can read something - even if there is no important information stored... So just put an ID in there. ;) Community email addresses: Post message: [email protected] Subscribe: [EMAIL PROTECTED] Unsubscribe: [EMAIL PROTECTED] List owner: [EMAIL PROTECTED] Shortcut URL to this page: http://groups.yahoo.com/group/php-list Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/php-list/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
