Gnus development mailing list
 help / color / mirror / Atom feed
From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Connecting to a newsserver with nntp.
Date: 22 Feb 1996 07:01:41 +0100	[thread overview]
Message-ID: <w8szqabkiey.fsf@aegir.ifi.uio.no> (raw)
In-Reply-To: gsstark@MIT.EDU's message of 21 Feb 1996 17:29:24 -0500

gsstark@MIT.EDU (Greg Stark) writes:

> 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.

That's true, but if one knows that a server doesn't answer pings, then
it is down (and vice versa, etc.), then it would be nice to be able to
ping the server first.  YMMV.  So adding a `nntp-ping-before-connect'
variable (nil by default) seems like a reasonable idea.

> 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?)

Yup.  I've written parts of if already, even.

--
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


  reply	other threads:[~1996-02-22  6:01 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
1996-02-22  6:01         ` Lars Magne Ingebrigtsen [this message]
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=w8szqabkiey.fsf@aegir.ifi.uio.no \
    --to=larsi@ifi.uio.no \
    /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).