Hi Adrien, thank you for your insights. I've some more questions inline.
Adrien de Croy: > * updates. Would need to poll or use long polling to get real-time > updates (e.g. notification of incoming mail). Could Websockets or http://en.wikipedia.org/wiki/Comet_(programming) be of help here? > * complex. In order to reduce round-trips, you'd have to do many things > in a single transaction, which would create complexity issues in the > server and client I was thinking restful HTTP which by definition is not complex. The question is, whether a useful mail fetch protocol could be designed in the constraints of rest. > I think it would also be very problematic in the wild, since any http > intermediary would feel entitled to mess with traffic. E.g. heuristic > caching, intercepting proxies etc. There is an HTTP header to instruct any cache to pipe the request through and do no caching. But anybody on any line in any protocol could mess with your data. Have to go now, sorry. :-) Best regards, Thomas Koch, http://www.koch.ro _______________________________________________ imap5 mailing list [email protected] https://www.ietf.org/mailman/listinfo/imap5
