Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: ding@gnus.org
Subject: Re: IMAP IDLE command
Date: Mon, 29 Nov 2010 16:10:43 +1100	[thread overview]
Message-ID: <m2lj4c3eb0.fsf@rimspace.net> (raw)
In-Reply-To: <m362vgbv9x.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Łukasz Stelmach <lukasz.stelmach@iem.pw.edu.pl> writes:
>
>> Does Gnus support IMAP IDLE[1] command for *notification* about new
>> messages?
>
> Nope.  Gnus really doesn't have any sort of mechanism for getting
> updates from the servers asynchronously.  But it'd be nice if it did.
>
> But I guess this can be pushed down into the backends without Gnus
> knowing anything about it.  I mean, nnimap could be using IDLE for
> notifications, and just keeping track of what the server says is
> happening.  A `g' from Gnus could then be basically a NOOP network-wise,
> and just give Gnus the info that's already been received by IDLE.
>
> I think.
>
> However, doesn't IDLE just give info about what's going on in a single
> mailbox?

Correct.  Which...

> That doesn't sound very useful.  But I dimly remember this being discussed
> before?

...is what we concluded last time, and indeed it isn't very useful.

> There's a new IMAP extension that'll output new data on all mailboxes?  That
> no IMAP servers implement yet?  Or something?

Basically, as far as I can tell.  Current "best practice" is one connection
per mailbox you want to monitor, which presumably does very bad things WRT
servers with connection limits.

        Daniel
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons




  reply	other threads:[~2010-11-29  5:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 17:09 Łukasz Stelmach
2010-11-28 17:31 ` Byung-Hee HWANG
2010-11-28 21:21   ` Łukasz Stelmach
2010-11-28 21:23   ` Łukasz Stelmach
2010-11-29  4:36 ` Lars Magne Ingebrigtsen
2010-11-29  5:10   ` Daniel Pittman [this message]
2010-11-29  6:21     ` Łukasz Stelmach
2010-11-29  7:38       ` Frank Schmitt
2010-11-29 21:25         ` Łukasz Stelmach
2010-11-29 21:37           ` Dan Christensen
2010-12-14 23:20     ` Ted Zlatanov
2010-12-15 19:34       ` Lars Magne Ingebrigtsen
2010-12-15 21:04         ` Ted Zlatanov
2010-11-29 21:39   ` Tibor Simko
2010-12-01  1:05     ` Łukasz Stelmach
2010-12-01  8:50       ` Steinar Bang
2010-12-02  0:12         ` Łukasz Stelmach
2010-12-02  9:07           ` Steinar Bang
2010-12-02 10:19             ` Łukasz Stelmach
2010-12-02 13:29               ` Steinar Bang
2010-12-02 18:25                 ` Łukasz Stelmach
2010-12-02 13:37               ` Julien Danjou
2010-12-02 18:13                 ` Łukasz Stelmach

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=m2lj4c3eb0.fsf@rimspace.net \
    --to=daniel@rimspace.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).