in reply to Is it harmful to spend too long on PerlMonks?

HTTP is a simple, stateless protocol which basically goes "client contacts server; client asks URI; server sends response; connection gets dropped".

"Logged on" cannot be compared with logging in using telnet, ssh, or on the console. "Logged on" just means "having send a request to the server in the past X minutes", for some X.

  • Comment on Re: Is it harmful to spend too long on PerlMonks?

Replies are listed 'Best First'.
Re^2: Is it harmful to spend too long on PerlMonks?
by Jenda (Abbot) on Oct 06, 2008 at 21:51 UTC

    Which doesn't mean leaving a browser window opened might not cause load on the server. The whole page or parts may be refreshed automatically, even if no one watches. The protocol is stateless, the browser is not. So on some sites enough forgotten windows may slow the server down.

Re^2: Is it harmful to spend too long on PerlMonks?
by herveus (Prior) on Oct 06, 2008 at 14:51 UTC
    Howdy!

    The oft-misapplied verb "log on" includes some manner of authentication. If I just visit a web site, I'm not "logged on" in any meaningful way. If I provide credentials, typically a user ID and password, *then* (and only then) have I "logged on".

    Advertisements that exhort me to "log on" to a web site are almost never using the right verb. "Visit" is far more appropriate in nearly every case.

    yours,
    Michael

      And don't get me started on the commercial I heard on the radio this morning exhorting me to "click on" blahdiblah.com . . .

      Then again if they understood how computers worked they wouldn't be stuck in marketing . . . :)

      The cake is a lie.
      The cake is a lie.
      The cake is a lie.