Hi all:
I'm in the design stage of creating a client-account management
system. We provide an array of support services to nonprofits, and I
wish to develop a system that is more than just a basic service
request system. I've been reading up on sessions management, as well
as cookies. I've also been combing through a number of similar
systems (either service request systems, or accounts management
systems).
My question is this: is there a specific reason to use a tracking
table in conjunction with session ids, other than knowing how often a
user logs in?
I ask, because a few of the systems I've examined have tracking
tables. But they all seem very brief just basically a trackid,
sessionid, userid, datetime, with one or two other fields.
I don't need to keep track of what each user is doing per say, but
I'm wondering if there have been other innovative uses of tracking
user sessions, that maybe I should consider. What types of things
would you use tracking for? and why?
Any comments would be appreciated.
Alnisa
--
.........................................
Alnisa Allgood
Executive Director
Nonprofit Tech
(ph) 415.337.7412 (fx) 415.337.7927
(url) http://www.nonprofit-techworld.org
(url) http://www.nonprofit-tech.org
(url) http://www.tech-library.org
.........................................
Nonprofit Tech E-Update
mailto:[EMAIL PROTECTED]
.........................................
applying technology to transform
.........................................
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
