see the archives about changes in priority of cookie vs. userreferenceargument.
there are some issues in migrating to W5, or running old aps. Also see the archive for session hijacking. >Hey all! > >I've recently encountered a problem, and I believe I know the reason, I just >wanted to take a quick poll of the list to make sure I'm on the right track. > >We've built a system that involves a user logon and maintenance of some user >variables. Occasionally we're running into a problem where a user in a >completely different geographic location picks up the variables from someone >else logged on. Unfortunately, we have no standard architecture for browser >requirements, so we could have the whole range from Opera to Firefox to IE >running, no to mention a wide range of security settings and firewalls set >up. > >Now, I believe that for whatever reason, the session cookie sent to the >browser is getting lost. Does this sound correct? I imagine the only cure >for this is to include a <@userreferenceargument> in every single URL >request we make with WiTango? Still sound correct? > >Let me know if you've had any experience in this particular area. > >Thanks! > >Jonah Simpson > >________________________________________________________________________ >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf Bill Conlon To the Point 345 California Avenue Suite 2 Palo Alto, CA 94306 office: 650.327.2175 fax: 650.329.8335 mobile: 650.906.9929 e-mail: mailto:[EMAIL PROTECTED] web: http://www.tothept.com ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
