MBOX-Line: From ladar at lavabitllc.com  Wed Mar 11 09:39:00 2015
To: imap-protocol@u.washington.edu
From: Ladar Levison <ladar@lavabitllc.com>
Date: Fri Jun  8 12:34:54 2018
Subject: [Imap-protocol] If Crispin were creating IMAP today how would
 it be different?
In-Reply-To: <18002.1426091085@parc.com>
References: <54FAEB94.4070508@lavabitllc.com> <54FBF289.3010202@psaux.com>
	<7164.1425831184@parc.com>
	<1425907661.1215497.237833469.1EDA571D@webmail.messagingengine.com>
	<6506.1425915329@parc.com> <55005876.4070406@lavabitllc.com>
	<18002.1426091085@parc.com>
Message-ID: <55006FA4.3090800@lavabitllc.com>

On 3/11/2015 11:24 AM, Bill Janssen wrote:
> I did say, "for instance".  A number of different database systems
> support replication, but replication for mobile is a harder problem.

Very true. As I recall Microsoft also has a DB replication/sync
framework that is supposed to work well over unreliable/slow network
links. I've never put their claims to the test though.

https://msdn.microsoft.com/en-us/sync/bb736753.aspx

> I should admit: we're experimenting with new email MUA.  I wrote the
> MDA to support it, and designed a custom (non-IMAP) MUA/MDA protocol to
> support unique features of the MUA -- and it doesn't use database
> replication.

Link? Or you keeping this piece of brilliance all to yourself?

I'm still looking for inspiration on my protocol design effort. I know
how to handle most of the functionality, but I'm still wrestling with
how to sync an encrypted binary file back to the server in a way that is
safe, and not overly complex... So when I hear "replication" I start to
think you may have the answer I'm looking for.

Of course before I worry about that problem I still need to decide which
scheme I'm going with. Lately I've been leaning towards sticking with a
line based protocol, aka, IMAP, but having it to send/receive JSON
objects...





-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20150311/cec8ca40/attachment.sig>
