Re: [Jmap] Review: draft-murchison-jmap-sieve-01

[Ken Murchison <[e-mail]>]

On 7/13/20 4:08 PM, Ricardo Signes wrote:
> *I suggest instead*:
>
> 1. We drop isActive as a property from SieveScript.
> 2. We create a new type, SieveConfig
> 3. SieveConfig has exactly one instance per account, with the fixed id 
> "singleton"
> 4. The SieveScriptConfig object has one property, activeScriptId, 
> which is either a script id or null
> 5. If no "name" is provided, the server will provide a guaranteed 
> unique name.
>
> To replace the active Sieve script in the blind, you do this:
>
> SieveScript/set { create: { newScript: { content: "..." } } }
> SieveConfig/set { update: { "singleton": { activeScriptId: 
> "#newScript" } } }
>
> This is guaranteed safe.  The worst case is that you end up with a 
> uniquely-named script that is not, in fact, active.
>
> We probably also need:
>
> 6.  If the active script is deleted, the SieveScriptActive 
> activeScriptId becomes null.
>
> Alternatively, it could be illegal to destroy the active script.


As an alternative to using a new data type for setting the active 
script, we could make isActive a server-set property (not directly set 
by the client within the SieveScript/set{create|update} method) and add 
a new onSuccessActivateScript argument to the SieveScript/set method 
which only gets processed if ALL create|update|delete are successful.

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC