Gnus development mailing list
 help / color / mirror / Atom feed
From: gsstark@MIT.EDU (Greg Stark)
Cc: pp@pfawww.pp.se, ding@ifi.uio.no
Subject: Re: Connecting to a newsserver with nntp.
Date: 21 Feb 1996 17:29:24 -0500	[thread overview]
Message-ID: <ycq7mxgwbwb.fsf@fierce-bad-rabbit.MIT.EDU> (raw)
In-Reply-To: eichin@cygnus.com's message of Wed, 21 Feb 96 14:56:18 EST


There are lots of problems with trying to determine if the host is up through
some other mechinism like ping.  Trusting two different protocols to agree
about whether the host is available is going to be inherently unreliable.
Ping itself is extrememely non-portable, it works differently under different
versions of Unix, and isn't available at all for some operating systems.

It's also not clear how long to wait for the ping response.  The same
arguments that justify(?) making the TCP timeout so large hold for ICMP
packets.  If Gnus has to wait for your modem to dial in an initiate a PPP
connection it could well take 30+ seconds before the first ping gets through.
I'm not sure why Linux thought the traditional 60 seconds was inadequate, but
there's no reason to think those arguments don't hold in this case.

The real answer regarding C-g is to implement asynchronous backend interfaces.
Then Gnus can initiate connections to the nntp backend and your mail backend
and allow you to read your mail while the nntp backend is still waiting to
time out.  Lars has already indicated that this is in the cards for Red Gnus.
(Right Lars?)

greg


  parent reply	other threads:[~1996-02-21 22:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-02-21 18:02 Per Persson
1996-02-21 18:39 ` eichin
1996-02-21 19:51   ` Per Persson
1996-02-21 19:56     ` eichin
1996-02-21 20:19       ` Per Persson
1996-02-22  1:12         ` Lars Magne Ingebrigtsen
1996-02-22  7:54           ` Per Persson
1996-02-22 18:03             ` Lars Magne Ingebrigtsen
1996-02-21 22:29       ` Greg Stark [this message]
1996-02-22  6:01         ` Lars Magne Ingebrigtsen
1996-02-22 23:28           ` Wes Hardaker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ycq7mxgwbwb.fsf@fierce-bad-rabbit.MIT.EDU \
    --to=gsstark@mit.edu \
    --cc=ding@ifi.uio.no \
    --cc=pp@pfawww.pp.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).