The web is stateless. This means the phone is hung up after every single
page call. After a call, the only means of keeping a user's context is
through session information, which is a kludge. If one examines it
objectively, there really is no state, as both sides are using persistent
data to store the information, but it appears as if there is state.
Having said that, without some form of beacon in the page, which would
entail either an ActiveX control, a Silverlight 1.1 control (beta still) or
a Java applet, there is no way to maintain communication. Even if you use
these techniques, you are not guaranteed a spot in line unless the piece on
the client side has a Dispose() method to send a beacon that it is being
killed. If you ask me, that is a lot of programming for little benefit.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
|
*************************************************
"Mufasa" <jb@nowhere.comwrote in message
news:uB**************@TK2MSFTNGP04.phx.gbl...
Does anybody have a slick way to tell if people are on the system. I have
a login so I can tell if a user is authenticated. What I've done now is
make a dataset that I store in the application variable and everytime
somebody loads a page, I update that dataset ( based on sessionid ) with
the time the user last loaded a page. When it reaches more the 20 minutes,
I make the assumption that the people must have gone elsewhere.
Just wondering if there is a slicker/better way to do this.
Any thoughts.
TIA - Jeff.