Quoth Rapscallion
View Post
That's right, it is I, the man with the power to confuse and bore you into a complete sleep.
Here's the rundown on why this is done.
The web browser talks to the web server using a method called HTTP (Hyper Text Transport Protocol). HTTP was defined to make a short connection to a remote server, retrieve data over that connection, and then close the connection.
This is different from instant messenger methods, which open a connection, and then leave that connection open. As a result, when the instant messenger connection is closed, you know that the program which was handling the instant messenging is no longer talking to the server in any way, and the person is definitely offline.
HTTP, though, is meant for you to read without being connected to the server. As a result, you might be reading a page from a thread for a good long while before you talk to the server again. As far as you're concerned, you're still online and active. However, the server doesn't know that.
So, what forum authors (and others) have done is to determine the longest time you are likely to be disconnected from the server while still reading content from that server. If you haven't gotten back in touch with the server after that time, it's a pretty safe bet that you're not actually reading the content, and are actually offline.
Now, if you'll excuse, the Home for Geriatric Insomniacs has asked me to do a talk about the many advantages of asynchronous transfer technology. Up, up, and away!
Comment