26 lines
1.1 KiB
Plaintext
26 lines
1.1 KiB
Plaintext
MBOX-Line: From janssen at parc.com Sun Mar 8 09:13:04 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: <54FBF289.3010202@psaux.com>
|
|
References: <54FAEB94.4070508@lavabitllc.com> <54FBF289.3010202@psaux.com>
|
|
Message-ID: <7164.1425831184@parc.com>
|
|
|
|
Messages in files is itself kind of old-school. There's still a place
|
|
for MUA/MDA separation, but perhaps the MDA should just be an SQL or
|
|
NoSQL database; dump all the messages in MySQL. Then the "access
|
|
protocol" would simply be the appropriate set of queries for whatever
|
|
the client is trying to achieve. The DB schema would define the protocol.
|
|
|
|
Triggers in the DB could do the thread calculation.
|
|
|
|
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
|
|
|