MBOX-Line: From dave at cridland.net  Tue May  3 01:27:17 2011
To: imap-protocol@u.washington.edu
From: Dave Cridland <dave@cridland.net>
Date: Fri Jun  8 12:34:45 2018
Subject: [Imap-protocol] Looking for help implementing an IMAP-to-HTTP
	gateway for web app developers
In-Reply-To: <7D2A9AA5-CC8F-4C8A-A917-4E242E7BCE12@gmail.com>
References: <7D2A9AA5-CC8F-4C8A-A917-4E242E7BCE12@gmail.com>
Message-ID: <2869.1304411237.632298@puncture>

The most successful parallel I've seen has been the dployment of XMPP  
on HTTP services. There, no attempt was made to translate between  
XMPP and "Web" paradigms, instead XMPP was wrapped into BOSH  
(XEP-0124), which basically provides the state and stream semantics  
that XMPP (and IMAP) needs.

This basically sidesteps the issues that Mark (rightly) raises, plus  
it means your problem becomes writing an IMAP client in Javascript.

XMPP/BOSH "connection managers" have been built independent of XMPP  
servers, so it should be reasonably possible to do the same for an  
IMAP/BOSH.

It'd allow for some very interesting webmail code.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

