JMAP for Sieve Scripts
Kenneth Murchison · 2000
This document specifies a data model for managing Sieve scripts on a server using JMAP. Open Issues o Do we need/want both and blobId in the SieveScript object? It may be simpler to have just one way of specifying content and blobId is more versatile and doesn't require JSON- encoding of the content. Furthermore, use of the forthcoming(?) Blob/set method would avoid the extra roundtrip of having to upload the blob first. o The strawman for SieveScript/test only uses blobIds. Will this have to change once the issue regarding content/blobId in SieveScript is resolved? o Should :fcc and associated arguments (e.g., :flags, :create:, etc) reported in the /test response be in their own fcc sub-object rather than listed inline with the rest of the arguments for the action?