[GitHub] [james-project] Arsnael commented on pull request #377: JAMES-3557 */changes: Fail explicitly when too much entries on a single change

[GitBox <gi...@apache.org>]

Arsnael commented on pull request #377:
URL: https://github.com/apache/james-project/pull/377#issuecomment-817525039


   > No not really. If the chunck is too large, the chunk is too large. The client should use a bigger /changes then.
   
   What is the point of having `hasMoreChanges` field and mechanic from the spec then if the chunk is too large we return an exception anyway? I'm trying to understand the logic behind this choice (and not about the technical limitations we might have from our code), which seems odd to me sorry


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org