You searched for the word(s): userid:70

More Search Options

RSS Available

• Re: User get same session id

  You mentioned you set cookieless=true. In the URL's used in the browsers of 1111 and 2222, do they both contain the same session id?

  Posted to State Management (Forum) by Patrick Y. Ng on 7/27/2004

• Re: session timeout in web.config question

  In v1 and v1.1, the session (and also the Cache engine) removed expired items using at timer that fires once every minute. So if you specify a expiration time of 2 minute, in reality your item will expire after a duration between 2 min and 2min 59 sec, depending on when you update your session.

  Posted to State Management (Forum) by Patrick Y. Ng on 7/26/2004

• Re: aspx files not found after VS 2005 installation

  For IIS6, you have to use "aspnet_regiis.exe -i -enable". This will automatically enable the asp.net web extension for you in IIS6.

  Posted to Installation and Setup (Forum) by Patrick Y. Ng on 7/23/2004

• Re: Session_End not fired on Session.Abandon

  Can you post a simple page and web.config that can repro the problem?

  Posted to State Management (Forum) by Patrick Y. Ng on 7/20/2004

• Re: Session_End not fired on Session.Abandon

  Please go to this FAQ and seach for the question "Q: Why isn't Session_End fired?" http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=7504

  Posted to State Management (Forum) by Patrick Y. Ng on 7/20/2004

• Re: why my session disappeared?

  Another possible reason is if the host have a frequent app-recycling policy. See this faq for more explanation: http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=7504

  Posted to State Management (Forum) by Patrick Y. Ng on 7/19/2004

• Re: Lock Cache

  It's safe. The truth is that when you call Cache.GetEnumerator, Cache will create a shallow copy of the hashtable that stores all its entries and return an enumerator based on that copy. But it's an expensive operation because it has to lock the Cache while copying.

  Posted to Web Forms (Forum) by Patrick Y. Ng on 7/16/2004

• Re: Cache, multithreading, and static methods

  All read or write accesses to Cache are thread-safe. However, to avoid the multiple writer problems you mention, use this classic approach: object myStuff = Cache["target"]; if (myStuff == null) { lock(somePrivateVar) { myStuff = Cache["target"]; if (myStuff == null) { myStuff = GenerateMyStuff(); Cache["target"] = myStuff; } } } This way, if you already have the item in the cache, you won't call the lock in every call.

  Posted to Web Forms (Forum) by Patrick Y. Ng on 7/16/2004

• Re: Is Session state thread safe?

  Session state implements a reader/writer lock for serialization. For details, see this faq: http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=7504

  Posted to State Management (Forum) by Patrick Y. Ng on 7/16/2004

• Re: StateServer drops session with Application Recycle

  This should not happen. Did you happen to restart aspnet_state too? Can you provide a sample (and simple) page + web.config that repros the problem?

  Posted to State Management (Forum) by Patrick Y. Ng on 7/16/2004