37 lines
1.2 KiB
Plaintext
37 lines
1.2 KiB
Plaintext
MBOX-Line: From ladar at lavabitllc.com Sat Mar 7 04:14:12 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?
|
|
Message-ID: <54FAEB94.4070508@lavabitllc.com>
|
|
|
|
I thought this might be a good list to ask a simple, but admittedly
|
|
subjective question: If Mark Crispin was creating IMAP from scratch, in
|
|
the world of today, would it still be a line based protocol like it was
|
|
with RFC3501, or would he have gone with something more stateless, like
|
|
a JSON-RPC paradigm, like JMAP?
|
|
|
|
For quick reference:
|
|
|
|
https://tools.ietf.org/html/rfc3501
|
|
|
|
Or JMAP:
|
|
|
|
http://jmap.io/spec.html
|
|
|
|
Or my own bastardized protocol used for webmail to server access, which
|
|
I created a few years back:
|
|
|
|
https://github.com/lavabit/magma.classic/raw/master/docs/magma.web.api.pdf
|
|
|
|
L~
|
|
|
|
-------------- 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/c129063a/attachment.sig>
|