foxcpp / go-jmap

:email: JMAP client & server library (WIP)

Hi there 👋

Contact info

• Email
• PGP: 34BB2007081396F4
• Telegram

go-jmap's Issues

Context support

Both for client and server side. For client - duplicate methods and add ctx argument. For server - pass context value to callbacks.

JMAP Core server implementation

Things to consider

Below are things I believe would make library more useful.

• go-jmap should avoid enforcing certain storage design and definitely must not provide storage implementation itself. I think it is best to simply translate API requests into corresponding method calls on some interface called "Backend" (see go-imap for a good example of how this could be done).

• go-jmap should avoid enforcing certain authentication design and definitely must not provide authentication implementation itself. As with previous point, authentication should be implemented by calling out into user-provided interface implementation.

• go-jmap should rely only on net/http for HTTP server. Use of more advanced frameworks will make it easier to violate the first point.

• JMAP Core, JMAP Mail, etc implementations should be kept independent of each other for extensibility purposes. JMAP is not only about email.

JMAP Core implementation

Reference: https://jmap.io/spec-core.html
List below is nowhere complete.

• Fundamental types
  • Int
  • UnsignedInt
  • Date
  • UTCDate
  • Id
• Autodiscovery
• Structures for base JMAP Core objects
  • Session
  • Account
  • Core Capabilities
  • Request-level errors
  • Invocation
    • Method-level errors
    • Decode Invocation "subtypes" using type -> decoder mapping.
  • Request
  • Response
  • Set-level errors
• Core request objects
  • Object/get
  • Object/changes
  • Object/set
  • Object/copy
  • Object/query
  • Object/queryChanges
• Core/echo
• Binary data I/O
  • Downloading
  • Uploading
  • Blob/Copy method
• Push
  • StateChange structure
  • PushSubscription structure
    • PushSubscription/get
    • PushSubscription/set
  • Event Source
• Client interface
  • Get Session object
  • Interface to send request objects directly
  • "Call batch builder" interface
  • Binary I/O interface
• Server interface
  • Base backend interface
  • Binary I/O backend interface
  • Method call dispatching