Bron Gondwana wrote: > By which time, why not just define a brand new protocol not called IMAP which > includes the good bits of what IMAP currently does, and discards anything that > doesn't fit the multi-folder worldview. So long as you made the storage and > meta-data requirements compatible with already existing Cyrus and other IMAP > servers, you could just write a whole new daemon that talked your new protocol > and be happy with that. > > Bron ( yes, I have been tempted to write something that talks sync_client protocol, > why do you ask ;) ISTR some talk a while ago about optimizing for webmail somehow; I think the proposal was to build-in an httpd that would work directly with the message store instead of having to go over IMAP. Along the lines of a custom protocol, I have been wondering if it wouldn't be more optimal to return JSON-encoded lists, instead of the usual IMAP response structure. With a webmail application that uses Ajax for folder and message lists and such, I would expect this could remove a considerable amount of processing on the web server itself. Wil
Attachment:
signature.asc
Description: OpenPGP digital signature
---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
