
May 11th, 2000, 07:07 AM
|
|
Contributing User
|
|
Join Date: Dec 2002
Posts: 14,575
  
Time spent in forums: < 1 sec
Reputation Power: 22
|
|
|
<i><b>Originally posted by : merLin (driggins@lockbox.com)</b></i><br />Mike,<br /><br />It's a weird problem that I wouldn't even attempt to solve for a couple of reasons. Cookies are not a solid way of getting information, for the fact many people do not accept them, and many people delete them quite often. Also if you are looking for scalability I would try using a db. But another simple solution would be to use a dictionary object, even though it is in essance a session variable, it executes extremely fast and is scalable. I won't go into details because there are already a lot of great articles about them, but if that doesn't work you could always revert to the querystring, scalable, and will work with load balancing as well. If you're using IIS5 / Win2k, just use Server.Transfer and you'll keep all your vars and data without having to do anything, but then again not everyone has Win2k yet.<br /><br />Hope that helps.<br /><br /> merLin<br /><br /><br />------------<br />Mike Green at 5/9/2000 5:01:31 AM<br /><br />Hi<br /><br />I'm currently using a mixture of Session vars and javascript cookies to keep the state of my web application. I've hit a problem, whereby when I write cookies using javascript (capturing the onload and onunload events) they 'sometimes' delete the Session state cookie so I loose all my Session vars.<br /><br />The cookie size is within the 4K limit. I chose to use cookies to store the majority of the application state so as not to clog up the web server with thread locking as the application must be scalable.<br /><br />Has anybody else expericened this problem before? What I cannot work out is why it only happens at random times which makes it even harder to fix.<br /><br />Any help or advice would be much appreciated<br /><br />Thanks<br /><br />Mike Green<br /><br />
|