It is a bit pricey, but ScaleOut StateServer supports this
quite well. I love the ability to share session variables
across servers and across app domains across servers.
Very powerful.
http://www.eggheadcafe.com/articles/scaleout_server.asp
--
Robbe Morris - 2004-2006 Microsoft MVP C#
I've mapped the database to .NET class properties and methods to
implement an multi-layered object oriented environment for your
data access layer. Thus, you should rarely ever have to type the words
SqlCommand, SqlDataAdapter, or SqlConnection again.
http://www.eggheadcafe.com/articles/..._generator.asp
"Bhavini" <Bhavini@discussions.microsoft.comwrote in message
news:1E8D0441-5795-49A0-A80B-5D255EA7718A@microsoft.com...
Quote:
Thx for the reply.
>
But actually we are having webfarm scenario, so I dont think it will be
possible to use caching here. And another thing is, we cant bear the delay
of
5 minutes. We should be able to login immediately once browser is closed.
>
Two scenarios I have in my mind
1) if we can catch browser close event and call logout process there. But
I
am not sure how to catch browser close event.
>
2) In DB we can maintain Active/Inactive flag as well as SessionID for
partucular user. So when the same user is logging we can check that
particualr session is activ or not based on session ID. I guess session ID
should be unique.
>
"Peter Morris [Droopy eyes software]" wrote:
>
Quote:
>Use the application cache with a sliding expiry of 5 minutes. At least
>this
>way your user will be locked out for a maximum of 5 minutes.
>Additionally
>I'd allow a duplicate login if it came from the same IP address.
>>
>>
>>