-----------------------------------------------------------

New Message on BDOTNET

-----------------------------------------------------------
From: Sitaraman
Message 2 in Discussion

Hi   Probably u r trying to prevent "ultiple Logins from the same user id"!!!! 
Right!!!!   Ok! Session_OnEnd has problems in StateServer & SQL based Session Mgmt.   
Check these out for the problem description and solution           "Preventing 
Multiple Logins in ASP.NET"  by "Peter A. Bromberg" : "The main issue is that if you 
put some sort of "lock" on the user record because somebody has logged in, and then 
they close their browser and you don't have a reliable way of determining that their 
session has expired so you can remove the lock, you are likely to get calls to your 
Tech Support desk from users complaining they cannot log in! (trust me, I have good 
reports that this has happened...) 
The big problem, it turns out, is that with StateServer and SQL Server Sessions, the 
Session_End event in Global is never fired. Only InProc mode fires this. So in order 
to avoid Tech Support coming after us with hatchets and knives, we would need to come 
up with some sort of reliable surrogate for the Session_End event.   Robbe took off on 
his own angle here and wrote an excellent article about using the Cache class to 
handle some of these issues. You can  read it here. Robbe also discusses how to use 
the callback mechanism in the Cache class to handle the situation where the item is 
removed from the Cache. In fact, he's determined that this even fires when the ASP.NET 
worker process recycles under normal conditions (such as when specified in 
machine.config), thereby enabling us to serialize Cache items to a database for later 
rehydration."
Link : http://www.eggheadcafe.com/articles/20030418.asp          
"Prevent Multiple Logins Using the Cache in ASP.NET" by By Robbe D. Morris : "In 
ASP.NET, the Session_OnEnd event appears to fire fairly consistently when using InProc 
as the Session management option.  However, if the ASP.NET worker process recycles, 
you are likely to get inconsistant results.  The Session_OnEnd event doesn't fire 
properly when utilizing State Server or SQL Server as the State management option.  
For many of us, this creates a real problem"
Link : http://www.eggheadcafe.com/articles/20030416.asp Related articles.  Gives u an 
alternate way of handling the problem 
hth regards,   sr

-----------------------------------------------------------

To stop getting this e-mail, or change how often it arrives, go to your E-mail 
Settings.
http://groups.msn.com/BDotNet/_emailsettings.msnw

Need help? If you've forgotten your password, please go to Passport Member Services.
http://groups.msn.com/_passportredir.msnw?ppmprop=help

For other questions or feedback, go to our Contact Us page.
http://groups.msn.com/contact

If you do not want to receive future e-mail from this MSN group, or if you received 
this message by mistake, please click the "Remove" link below. On the pre-addressed 
e-mail message that opens, simply click "Send". Your e-mail address will be deleted 
from this group's mailing list.
mailto:[EMAIL PROTECTED]

Reply via email to