49 lines
1.5 KiB
Plaintext
49 lines
1.5 KiB
Plaintext
MBOX-Line: From snowjn at aol.com Sat Mar 7 09:36:36 2015
|
|
To: imap-protocol@u.washington.edu
|
|
From: John Snow <snowjn@aol.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: <54FAEB94.4070508@lavabitllc.com>
|
|
References: <54FAEB94.4070508@lavabitllc.com>
|
|
Message-ID: <54FB3724.2070202@aol.com>
|
|
|
|
If he were around, this question would have started a fun argument.
|
|
I miss that guy.
|
|
|
|
snow.
|
|
|
|
|
|
On 3/7/2015 7:14 AM, Ladar Levison wrote:
|
|
> 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~
|
|
>
|
|
>
|
|
>
|
|
> _______________________________________________
|
|
> Imap-protocol mailing list
|
|
> Imap-protocol@u.washington.edu
|
|
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
|
|
|
|
-------------- next part --------------
|
|
An HTML attachment was scrubbed...
|
|
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20150307/fb819105/attachment.html>
|