Re:JMAP: Like IMAP but Not Really
by chrismorgan on Monday January 28, 2019 @06:33PM
(#19022185)
Understand that JMAP is an object synchronisation protocol. It’s most interested in the problems that are out of scope for GraphQL.
You could have a variant of JMAP with GraphQL syntax and semantics, but there would be a fair bit of mismatch, for their purposes and focuses are quite different: JMAP is concerned with object identity and synchronisation, for what you might call thick clients (and JMAP Mail needs to be broadly IMAP compatible), while GraphQL is UI-focused, for what might reasonably be considered to be thin clients (not that they are logicless, but that they are very much focused on offloading burden to the server). I see no compelling case for a JMAP-like GraphQL thing.
It could still be an interesting task to develop a object synchronisation protocol like the JMAP core on top of GraphQL.
You could have a variant of JMAP with GraphQL syntax and semantics, but there would be a fair bit of mismatch, for their purposes and focuses are quite different: JMAP is concerned with object identity and synchronisation, for what you might call thick clients (and JMAP Mail needs to be broadly IMAP compatible), while GraphQL is UI-focused, for what might reasonably be considered to be thin clients (not that they are logicless, but that they are very much focused on offloading burden to the server). I see no compelling case for a JMAP-like GraphQL thing.
It could still be an interesting task to develop a object synchronisation protocol like the JMAP core on top of GraphQL.