Like I said - I've never seen a system like this reliably implemented. The issue is that when the user leaves your site, you generally don't know until their session expires. You could of course use some kind of javascript onpageunload.
Personally, I've yet to see a real business case that requires this functionality - have you ascertained that you absolutely need this? On Mon, Sep 27, 2010 at 12:03 PM, VB <[email protected]> wrote: > I don't think its the right way ...because we have certain cases in > our mind where it will be a flop-show....like user's system is getting > hanged or crash etc... so its not reliable way... :( > > > On Sep 27, 1:59 pm, Jamie Fraser <[email protected]> wrote: > > Store a value somewhere shared (DB) that is set to 1 when a user logs > into a > > system. Set this value to 0 when they logout or the session expires. > Check > > this value on login, if it is already 1, then prevent login. > > > > Sounds like a bit of an annoying system though, and not one I've seem > > implemented properly. > > > > > > > > On Mon, Sep 27, 2010 at 7:31 AM, VB <[email protected]> wrote: > > > Hi, > > > I want to restrict user to logged-in on one system at a time...means > > > if user logged-in a system then same user will not allow to logged-in > > > on another system until logoff from first system... > > > I want to know the concept...what should i do ? > > > Im using ASP.NET 3.5 with C# > > > > > Regards, > > > VB- Hide quoted text - > > > > - Show quoted text -
