I use mod_usertrack in apache, combined with standard log analysis tools. There's no need to reinvent all this stuff. mod_usertrack does a pretty good job of guaranteeing unique ids. To integrate it with zope, you can run reports on a cron job and view the HTML output as a LocalFS view. Don't forget to make sure apache is proxying your requests, or your cookies won't get set. Here's my VHost directive: <VirtualHost 192.168.0.10> ProxyRequests On CacheSize 50000 CacheGcInterval 10 CacheMaxExpire 1 CacheRoot /var/apache/cache CacheForceCompletion 100 CacheDefaultExpire 1 ServerAdmin root@localhost ServerName dev.foo.jamkit.com DirectoryIndex index_html RewriteEngine on RewriteRule ^/images/ - [L] RewriteRule ^/(.*) http://127.0.0.1:8001/VirtualHostBase/http/dev.breastcancercare.jamkit.com:8... [P] CookieExpires "5 years" CookieName foo_userid CookieTracking on </VirtualHost> seb * Trevor Toenjes <zope@toenjes.com> [010906 20:22]:

My latest newbie challenge...! Has anyone implemented an extensive user tracking system with Zope? Is this built into Zope anywhere?

I am looking for the right combo of products and how-to's to figure this out. Should I use ZODB or zSQL, or pgSQL, etc? What performance problems will Zope have? forcing external methods, etc?

I figured to use a permanent cookie (because I cant force a login) to assign a GUID (global user id) and then track everything the user ever does (click-stream)and when. Then correlate form data(surveys/polls, etc) with the GUID. I think this is different from blogging??? because the tracking is specific to the GUID/cookie. and not an IP.

I would love some advice to generate the GUID itself too, so it cant be hacked and would never generate the same number twice..

whew...Thanks soo much for any feedback, Trevor