MBOX-Line: From dave at cridland.net  Tue Aug 31 00:52:36 2010
To: imap-protocol@u.washington.edu
From: Dave Cridland <dave@cridland.net>
Date: Fri Jun  8 12:34:45 2018
Subject: [Imap-protocol] "Multiple Commands in Progress" real life
	support and ambiguity questions
In-Reply-To: <AANLkTi=P4xykgMBBrtPd1=DG5pN8fTUOqg4ZY-pteJVr@mail.gmail.com>
References: <4C7A2AB6.6070405@lists.grepular.com>
	<alpine.OSX.2.00.1008291038500.370@hsinghsing.panda.com>
	<2721.1283156569.612563@puncture> <4C7C2DB1.6020107@lists.grepular.com>
	<AANLkTi=P4xykgMBBrtPd1=DG5pN8fTUOqg4ZY-pteJVr@mail.gmail.com>
Message-ID: <2639.1283241156.558227@puncture>

On Mon Aug 30 23:20:01 2010, Yiorgos Adamopoulos wrote:
> On Tue, Aug 31, 2010 at 1:16 AM, Mike Cardwell
> <imap-protocol@lists.grepular.com> wrote:
> > supports it... JOOI, what client implementations are there for  
> ACAP?
> 
> http://dave.cridland.net/acap/polymer.html

Polymer's an aquired taste... :-)

Mulberry supports it, kind of, as does Wanderlust (an Emacs thing),  
and Eudora. None of them support the standardized datasets proposed  
in I-D forms for configuration, though, as I recall.

Speaking as someone who's implemented both ends of it, and still uses  
it in production, I have to say I wouldn't bother now. There are  
several features of ACAP I do think are highly beneficial, including  
the ability to push configuration (etc) updates to aware clients, and  
the promise of interoperability with basic configuration data, but  
there are shortfalls in the protocol's infrastructure which I think  
modern data-sharing protocols address much better, most especially  
the initial discovery and bootstrap.

In particular, I'd be inclined to use XMPP, and more specifically  
PEP/PubSub, in its private data store mode, if I were doing all this  
again. I'm intending tackling this one relatively shortly. The  
benefit there is that you're using a protocol you can bootstrap into  
purely off a jid and a password, say "I care about X Y and Z", and  
have the server not only send you your data, but everyone else's who  
wants to share it with you.

However, should we ever tackle an IMAP5, I would definitely mine ACAP  
for various features of its protocol syntax. It's a very nicely  
designed protocol, and the data model (in respect to searching etc)  
is very neat.

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

