From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: IMAP and IDLE...
Date: Thu, 17 Mar 2011 13:31:12 -0500 [thread overview]
Message-ID: <87ei6538gf.fsf@lifelogs.com> (raw)
In-Reply-To: <sdpqpptyaz.fsf@wjh.hardakers.net>
On Thu, 17 Mar 2011 11:08:20 -0700 Wes Hardaker <wes@hardakers.net> wrote:
WH> So, the trick to mail (and I get tons) is still server-side-filtering.
WH> I cringe at the thought of everyone doing client side filtering and
WH> watching it all get sucked in and then filtered as they wait.
Oh, once you've used `gnus-registry-split-fancy-with-parent' you can
never go back ;)
This is actually on my TODO list for Cloudy Gnus: move the registry to
a shared storage mode so non-Gnus clients can figure out the right
mailbox for a reply.
On Thu, 17 Mar 2011 11:11:05 -0700 Wes Hardaker <wes@hardakers.net> wrote:
WH> Maybe the right thing to do is do IDLE by default on INBOX (which,
WH> ironically, I don't use at all) and then have a group parameter (or
WH> something) set to open a new connection specifically for that box. That
WH> way you could set the 'this box is important flag' on it to do IDLE
WH> updates for, say, the top 10 boxes out of the 100 that you might have?
WH> And the 11th for all the rest (or the 11th is the INBOX IDLE one that is
WH> also the main pull connection).
How about making IDLE-handlers an alist of (folder . handler) pairs?
When it's a single symbol or lambda you know it's for "INBOX".
Then if the user asks for 800 IDLE connections, well, they asked for it...
Ted
next prev parent reply other threads:[~2011-03-17 18:31 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 [this message]
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
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=87ei6538gf.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).