Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Process imap not running
Date: Thu, 17 Jan 2008 22:58:59 -0600	[thread overview]
Message-ID: <m2abn3n2zw.fsf@lifelogs.com> (raw)
In-Reply-To: <v9odbkfgiw.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 17 Jan 2008 19:33:59 +0100")

On Thu, 17 Jan 2008 19:33:59 +0100 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 

RS> On Thu, Jan 17 2008, Ted Zlatanov wrote:
>> On Wed, 16 Jan 2008 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 
RS> On Tue, Jan 15 2008, Ted Zlatanov wrote:
>>>> On Tue, 15 Jan 2008 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 
RS> I added the variable `imap-ping-server', defaulting to t.  Please
RS> adjust if necessary.
>>>> 
>>>> I think it should be an integer, representing the minimum number of
>>>> seconds 

RS> ... better use milliseconds or allow floats?

OK.

>>>> before it's triggered (or nil to turn it off).
>> 
RS> Is this feasible?  Would someone like to implement this?
>> 
>> I could do it eventually, 

RS> Please do.

I'll put it on my TODO list.

>> but it's really not too hard.  Just make a buffer-local timer in the
>> imap buffer and check it every time if the variable is not t.

>>>> The default should be nil.  When the IMAP server is far away, pinging
>>>> the server introduces a painful delay because of the TCP round trip.
>> 
RS> Could you explain how much delay it cause (and when)?  As it seems to
RS> fix a problem for several users, it would be nice to set it to t.

RS> ... or some reasonable integer?

>> Remote TCP connections require an acknowledgment for every packet.  [...]

RS> My question aimed at your personal experience, i.e. which Gnus/IMAP
RS> commands are noticeably slower (getting new articles, displaying
RS> articles, ..., more or less all commands?) and how long the delay is
RS> approximately (several seconds?).

(sorry for the discourse)

I haven't noticed it personally, since I use IMAP servers that are
nearby on fast links.  Generally it wouldn't be directly noticeable
since the delay is small per command on the average, but on the whole
the users will have a slower experience, and in the worst case (on a
slow link to a distant server) it will surely be unpleasant.

Ted



      reply	other threads:[~2008-01-18  4:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06  9:38 Ralf Angeli
2008-01-10 12:19 ` Knut Anders Hatlen
2008-01-11 13:58   ` Andreas Jaeger
2008-01-14 19:12   ` Ralf Angeli
2008-01-14 20:33     ` Reiner Steib
2008-01-14 20:57       ` Simon Josefsson
2008-01-14 23:27         ` Reiner Steib
2008-01-15 21:08           ` Ted Zlatanov
2008-01-16 22:50             ` Reiner Steib
2008-01-17 14:36               ` Ted Zlatanov
2008-01-17 18:33                 ` Reiner Steib
2008-01-18  4:58                   ` Ted Zlatanov [this message]

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=m2abn3n2zw.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /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).