Benoit Tellier created JAMES-3552:
-------------------------------------
Summary: Enforce session advertised limits
Key: JAMES-3552
URL: https://issues.apache.org/jira/browse/JAMES-3552
Project: James Server
Issue Type: Sub-task
Components: JMAP
Reporter: Benoit Tellier
Assignee: Antoine Duprat
Fix For: 3.6.0
We advertize a bunch of limits in the session:
{code:java}
"urn:ietf:params:jmap:core" : {
"maxConcurrentUpload" : 4,
"maxSizeRequest" : 10000000,
"maxConcurrentRequests" : 4,
"maxCallsInRequest" : 16,
"maxObjectsInGet" : 500,
"maxObjectsInSet" : 500
},
"urn:ietf:params:jmap:mail" : {
"maxMailboxesPerEmail" : 10000000,
"maxMailboxDepth" : null,
"maxSizeAttachmentsPerEmail" : 20000000
}
{code}
- maxMailboxesPerEmail can likely be null if not enforced
Regarding maxConcurrentUpload and maxConcurrentRequests enforcing these
limitations in a distributed environment is a non trivial task... Maybe via the
use of external API management solutions? In which case we should allow an
administrator to configure those values according to system wide setting...
maxSizeRequest, maxCallsInRequest, maxObjectsInGet, maxObjectsInSet,
maxSizeAttachmentsPerEmail would likely only need some simple validation logic
to be written.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
