Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
To: ding@gnus.org
Subject: Re: IMAP and IDLE...
Date: Thu, 17 Mar 2011 11:11:05 -0700	[thread overview]
Message-ID: <sdlj0dty6e.fsf@wjh.hardakers.net> (raw)
In-Reply-To: <m3tyf3arv1.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 16 Mar 2011 18:37:54 +0100")

>>>>> On Wed, 16 Mar 2011 18:37:54 +0100, Lars Magne Ingebrigtsen <larsi@gnus.org> said:

LMI> You can only IDLE on one mail box per connection.  It's a pretty stupid
LMI> limitation in the IMAP protocol, but...

There are proposals to add a multiple-idle command to fix this.  But I
don't think it's implemented anywhere yet (but haven't checked).

The way other mail systems get around this is to open multiple
connections.  Sucks, I know, but is still the only solution.

Maybe the right thing to do is do IDLE by default on INBOX (which,
ironically, I don't use at all) and then have a group parameter (or
something) set to open a new connection specifically for that box.  That
way you could set the 'this box is important flag' on it to do IDLE
updates for, say, the top 10 boxes out of the 100 that you might have?
And the 11th for all the rest (or the 11th is the INBOX IDLE one that is
also the main pull connection).
-- 
Wes Hardaker                                     
My Pictures:  http://capturedonearth.com/
My Thoughts:  http://pontifications.hardakers.net/



  parent reply	other threads:[~2011-03-17 18:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 11:31 Lars Magne Ingebrigtsen
2011-03-16 11:43 ` Greg Troxel
2011-03-16 13:46   ` Frank Schmitt
2011-03-16 13:53 ` Ted Zlatanov
2011-03-16 13:58   ` Lars Magne Ingebrigtsen
2011-03-16 14:37     ` Eric S Fraga
2011-03-17 18:08       ` Wes Hardaker
2011-03-17 18:31         ` Ted Zlatanov
2011-03-17 20:52           ` Wes Hardaker
2011-03-17 21:04             ` Ted Zlatanov
2011-03-18  8:51         ` Eric S Fraga
2011-03-18 14:36           ` Wes Hardaker
2011-03-18 16:00             ` Eric S Fraga
2011-03-19  0:28               ` Wes Hardaker
2011-03-21 10:57               ` Julien Danjou
2011-03-21 14:15                 ` Eric S Fraga
2011-03-16 14:20   ` Olivier Sirven
2011-03-16 14:28     ` Ted Zlatanov
2011-03-16 17:35       ` Lars Magne Ingebrigtsen
2011-03-16 18:48         ` Ted Zlatanov
2011-03-17 17:18           ` Lars Magne Ingebrigtsen
2011-03-17 17:31             ` Ted Zlatanov
2011-03-17 17:44               ` Lars Magne Ingebrigtsen
2011-03-17 18:24                 ` Ted Zlatanov
2011-03-16 14:13 ` Olivier Sirven
2011-03-16 17:37   ` Lars Magne Ingebrigtsen
2011-03-16 18:28     ` Olivier Sirven
2011-03-16 18:34       ` David Engster
2011-03-17 18:11     ` Wes Hardaker [this message]
2011-03-17 18:14       ` Lars Magne Ingebrigtsen
2011-03-17 20:53         ` Wes Hardaker
2011-03-29 19:14           ` Lars Magne Ingebrigtsen
2011-03-16 20:21 ` John Sullivan
2011-03-17 17:19   ` Lars Magne Ingebrigtsen
2011-03-17 20:30     ` James Cloos
2011-03-29 19:13       ` Lars Magne Ingebrigtsen
2011-04-01 23:11         ` John Sullivan

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=sdlj0dty6e.fsf@wjh.hardakers.net \
    --to=wes@hardakers.net \
    --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).