On Fri, Feb 24, 2012 at 12:29 PM, Adrien de Croy <[email protected]> wrote: > > The obvious application for server-side parsing is providing the ability to > search the store without having to download the whole thing first. In many > cases it's simply not possible otherwise. > > I think it's a very compelling feature. Which for me means server-side > parsing should stay. > > One could argue that to a certain level it could be simplified. Providing a > complete nested body structure is only really relied on by some clients. > Many just download the whole, or parts and then parse client-side. > > But I don't know to what level, and since we have an existing working > mechanism. > > As for always connected vs offline & connect-as-required. I think these are > 2 useful cases. In-house corporate use can benefit from always connected, > but it doesn't scale well for huge providers. Being able to re-establish > some state without having to go through the whole setup phase could be an > interesting option to look into, e.g. some reusable token (good for a > certain amount of time since last use) would allow the server to cache the > "session" and the client to re-establish quickly.
That was in the P-IMAP proposal, which I assume means it was discussed in lemonade, anyone recall why it didn't go anywhere? Granted, with qresync/condstore, session maintenance probably isn't as important. Brandon _______________________________________________ imap5 mailing list [email protected] https://www.ietf.org/mailman/listinfo/imap5
