[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lemonade] draft-gulbrandsen-imap-notify-01 use cases
Hi,
I try to understand the use cases and purpose of
draft-gulbrandsen-imap-notify-01.
Is it correct that the primary goals are mainly the two following points?
1. being able to restrict the amount of data IDLE [RFC2177] would send
downstream by issueing the NOTIFY command with appropriate parameters
2. theses restrictions can be used during IDLE or always
3. allow for reducing the load on the server by avoid unnecessary notification
messages
To me this looks like it is mainly emphasizing on improving the downstream
bandwidth usage while helping the server to avoid doing unnecessary work.
Did I miss further goals/use cases?
In addition I want to solve some further goals with IDLEPLUS. The general
use-cases which IDLEPLUS tries to solve are:
1. improve the performance with high latency and asymmetric TCP/IP
connections. A typical use case would be IMAP over an UMTS link with
typically 384 k/Bit downstream but often only 64 k/Bit upstream.
2. avoid transfering upstream (C->S) the redundant data and therefore make use
of server side configuration store (subscribe db and METADATA annotations if
available)
3. allow to monitor a potentially high number of mailboxes while leveraging on
the fact that generally most mailboxes are idle (*)
4. allow for efficient implementation on both server and client. (Actually I
am currently working on an implementation for Cyrus Imapd)
I can easily imagine to merge these two efforts. Especially I am more than
willing to add support for being able to make the type of notifications
configurable. This can be either done like in NOTIFY using parameters or
preferably using annotations and leveraging upon the METADATA extension.
After reading the recent minutes
http://tools.ietf.org/wg/lemonade/minutes?item=minutes67.html I got the
impression that actually the scope of NOTIFY shall be extended to allow
monitoring multiple mailboxes in parallel. I guess that this change is in the
pending -02 version of draft-gulbrandsen-imap-notify.
On the other hand I am wondering if the use cases being addressed in IDLEPLUS
can also be implemented in NOTIFY?
Opinions welcome!
(*) a typical use case is a CRM system with a subfolder for each customer.
This can result easily into many thousand folders though most of the time
nothing actually changes.
http://www.erfrakon.de/konold/draft-konold-imap-idleplus-04.txt
Yours,
-- martin
--
http://www.erfrakon.com/
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
_______________________________________________
lemonade mailing list
lemonade at ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade