From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: broken server [SERVER][DEAF]
Date: Thu, 11 Apr 2002 19:37:11 +0200 [thread overview]
Message-ID: <vaflmburvaw.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87k7rggn80.fsf@ketanu.dyndns.org>
Ketanu <ketanu@wanadoo.fr> writes:
> Deaf : the conenction is still alive (as shown with a banal traffic
> sniffer) so i believe the server did not close it, but it do not
> respond anymore to any request, so i say it is deaf. This is rather
> nasty since trying to refetch or post after 120s of inactivity (wuw,
> i will become flash typo if i can write all my articles in less than
> 120s), and since the conenction is not technically down, the
> nntp-connection-timeout parameter is useless (or do not work on my
> computer)
I think it would be best to do the following: Before sending a
command to the server, Gnus looks how long ago was the last command
sent. If this was more than N seconds ago, send a no-op command to
the server and look for the response. If the response does not come,
look again if the server is really alive.
This could be useful for IMAP, too, not only NNTP.
kai
--
Silence is foo!
parent reply other threads:[~2002-04-11 17:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87k7rggn80.fsf@ketanu.dyndns.org>]
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=vaflmburvaw.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).