MBOX-Line: From janssen at parc.com  Wed Mar 11 09:24:45 2015
To: imap-protocol@u.washington.edu
From: Bill Janssen <janssen@parc.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: <55005876.4070406@lavabitllc.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>
Message-ID: <18002.1426091085@parc.com>

Ladar Levison <ladar@lavabitllc.com> wrote:

> On 3/8/2015 11:13 AM, Bill Janssen wrote:
> > And let the DB guys solve the intermittent connection problems :-).
> > Oracle, for instance, has a "Mobile Server" product that synchonizes a
> > local cache on a mobile device with a remote Oracle DB, including SSL
> > encryption on the sync connection, and data compression.
> >
> 
> Bill, how much is Larry paying you?
> 
> It might be fun to submit an RFC draft that "mandates" the use of
> something like the Oracle Mobile Server. Or heck, requires everyone
> install Panagon on their machine to access their email - just to hear
> the groans. If carrier pidgeons can make it past the rfc-editor then why
> not?
> 
> :)

I did say, "for instance".  A number of different database systems
support replication, but replication for mobile is a harder problem.

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.

Bill

> 
> On a slightly more serious note, Dovecot has a protocol for syncing
> message stores, but I haven't studied it closely yet.
> 
> L~
> 
> 
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol

