51 lines
2.4 KiB
Plaintext
51 lines
2.4 KiB
Plaintext
MBOX-Line: From ladar at lavabitllc.com Sat Mar 7 08:10:19 2015
|
|
To: imap-protocol@u.washington.edu
|
|
From: Ladar Levison <ladar@lavabitllc.com>
|
|
Date: Fri Jun 8 12:34:53 2018
|
|
Subject: [Imap-protocol] If Crispin were creating IMAP today how would
|
|
it be different?
|
|
In-Reply-To: <CAKHUCzzirU0YEQ02n1zEypZCvUJ+0dU0CuPxT=ZnowTk_R6jOg@mail.gmail.com>
|
|
References: <54FAEB94.4070508@lavabitllc.com>
|
|
<CAKHUCzzirU0YEQ02n1zEypZCvUJ+0dU0CuPxT=ZnowTk_R6jOg@mail.gmail.com>
|
|
Message-ID: <54FB22EB.7090707@lavabitllc.com>
|
|
|
|
|
|
|
|
On 3/7/2015 8:34 AM, Dave Cridland wrote:
|
|
> But in the world of today, the elephant is that the bulk of mail is
|
|
> under the control of a handful of huge providers, and a guy working in
|
|
> a university lab somewhere is pretty unlikely to have the chance to
|
|
> make any kind of difference, and probably wouldn't be interested.
|
|
> Mark, in his twenties, tended to solve practical problems that he
|
|
> encountered, like telnet issues, roaming mail users, etc. Those
|
|
> problems are already solved, so I suspect he'd be solving some
|
|
> entirely different problem today, like WebRTC signaling, or practical
|
|
> end to end crypto, or secure file sharing, or heaven only knows what.
|
|
|
|
If all those big providers were using POP, and he wanted to solve a
|
|
problem, like mobility, would he have approached it differently? From an
|
|
abstract standpoint, the programming language doesn't matter. IMAP is a
|
|
protocol that can be implemented in any language, which holds true for
|
|
JSON protocols as well. They are simply schemes for stateless
|
|
client/server interactions (stateless because they have to go over HTTP)
|
|
and which happen to use JSON as the serialization scheme. They could
|
|
just as easily have used SOAP/XML.
|
|
|
|
I'm wondering if the future of mail protocols is to continue improving
|
|
the line based protocols we have, or will they be replaced by something
|
|
that is friendly to the web? Were seeing a number of vendor specific
|
|
mail protocols already, and I'm wondering if convergence is in our
|
|
future? In other words, if someone were to start working on a new
|
|
protocol today, should they focus on the old line based scheme, or
|
|
switch to the newer stateless, JSON paradigm common to the web?
|
|
|
|
|
|
|
|
-------------- 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/20150307/aadb9bbe/attachment.sig>
|