|
|
|
|
|
by userbinator
539 days ago
|
|
This? https://en.wikipedia.org/wiki/JSON_Meta_Application_Protocol They cited IMAP's complexity, high resource use, JMAP is implemented using JSON APIs over HTTP They complain about complexity, then add another two layers of complexity in their own protocol? I think POP3 is the simplest standard, and have also written a basic IMAP client. Parsing IMAP isn't as easy as a binary protocol, but it's definitely not at the level of HTTP JSON bloat that seems to have infected all "modern" protocol designers. I can use POP3 reasonably easily from a netcat (and have done so many times in the past), and IMAP is a little harder but doable. I don't expect that to be doable for JMAP which is text-based like the other HTTP JSON bloatocols, but unlike the earlier text-based standards like SMTP POP3 IMAP IRC MSNP etc., it seems to have all the disadvantages of a text-based protocol but none of the advantages. |
|