Benoit Tellier created JAMES-3540:
-------------------------------------
Summary: Spec compliance: Blob/copy
Key: JAMES-3540
URL: https://issues.apache.org/jira/browse/JAMES-3540
Project: James Server
Issue Type: Sub-task
Components: JMAP
Affects Versions: 3.6.0
Reporter: Benoit Tellier
Assignee: Antoine Duprat
https://jmap.io/spec-core.html#blobcopy
{code:java}
Binary data may be copied between two different accounts using the Blob/copy
method rather than having to download and then reupload on the client.
{code}
Our JMAP implementation (and the underlying right system backing it) do not
support multi-account. Making this methods globally useless.
However, in the sake of spec compliance, we might consider expose a naive
version of it:
Quoting https://jmap.io/spec-core.html#copy
{code:java}
accountId: Id The id of the account to copy records to. This MUST be different
to
the fromAccountId.
{code}
As we currently enforce accountId to match the user account, we can:
- Reject with invalidArguments if accountId is the user one and fromAccountId
also the user one.
- Reject with accountNotFound if accountId do not match the user one
- Reject with fromAccountNotFound if fromAccountId is different from the user
accountId.
Not really useful, but it would technically be specification compliant...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
