On Thu Feb 9 11:25:33 2012, Giovanni Panozzo wrote:
Http is also "stateless" from its birth: the advantage is that we
can better serve clients with intermittent connections (point 3 in
Bron's list), like mobile phones or poorly connected wifi laptops.
This one's a myth.
We've had BOSH in the XMPP world for a while, and although it's used
in the web browser, it's typically avoided in mobile because it ramps
up the power requirements quite heavily, and turns out to to no more
effective than the newer XEP-0198 anyway.
It'd be much better for web clients to run actual IMAP over either
BOSH or Websocket. The difficulty with this approach is twofold:
1) IMAP transfers binary data in-line, and Javascript simply doesn't
cope well with this.
2) Parsing IMAP in Javascript means parsing it with a pure Javascript
parser, which will be slower and more prone to error. Using XML or
JSON would be better here.
To address both, I think I could build a useful IMAP replacement that
ran the metadata, push, and folder management over XMPP, and the
content access over HTTP, quite easily. It's almost tempting, and is
at least as perverse as the other proposals.
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
imap5 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imap5
