On Wednesday, October 13, 2004, at 10:26 AM, Roland Dumas wrote:
Case 1: spidered session has expired. Someone hits the link with the
expired
userref and has cookies off. I believe they just revived that session -
started another with the same id.
They have only revived this in the sense that the userreference will
appear multiple times in the log. That's a housekeeping issue only.
But, if that userreference is in google, for example, and User1, User2,
etc., all follow a link containing the same userreference, then you
have a problem.
I'm still waiting for an explanation as to why there would be a problem.
The only way that there would be a problem, that I can see, is if the
Witango server assign both Google visitors to the same new userref
that was generated for the first visitor. Is this the way that the server
works? Otherwise, I would think that the server would evaluate whether
a session had expired for each visitor separately and assign new userrefs
for each.
I know that Scott is saying to just stopping worrying about it and drop
userrefs, but I want to understand the situation so that I will know web
programming. :) Please, someone respond to my specific question.
Thanks,
Stefan
Database WebWorks: Dynamic web sites through database integration
http://www.DatabaseWebWorks.com
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
