Quoting Paul A Sand <p...@unh.edu>:
Upside: it convinced me that our bottleneck wasn't "between" IMP and UW-IMAP, it was UW-IMAP. Even if you can't replace UW-IMAP yourself, you might be able to use the results to convince those other admins to do so.
The important thing to remember is that UW-IMAP was extremely tied into the spirit of IMAP4. And the underlying idea of IMAP4 is that mail clients will connect once to the server and maintain that connection for an extended period of time. Disconnected clients (of which webmail is a type) are inapposite of this thinking. Extensions have been made to IMAP since this time to deal with this ever popular connection style (e.g. LEMONADE group), but UW-IMAP doesn't support these extensions and other features designed to speed access to disconnected clients (e.g. server-side caching).
IMP can work around some of these limitations internally. However, IMP is limited to the amount of caching it can realistically do since it works under some fairly strict resource limitations (e.g. limited amount of memory due to the fact a single server may be handling tens/hundreds of IMP connections a second).
michael -- ___________________________________ Michael Slusarz [slus...@horde.org] -- IMP mailing list Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: imp-unsubscr...@lists.horde.org
