[
https://issues.apache.org/jira/browse/JAMES-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319058#comment-17319058
]
Daniel Gultsch commented on JAMES-3562:
---------------------------------------
{quote} We should change the behaviour to a simple "cannot calculate changes."
That would be a better naive implementation IMO
{quote}
For my implementation specifically this would honestly just make it worse.
The current situation just triggers a rather unexpected fetch of missing
threads after a query update (I would have expected to already know about the
thread because of Thread/changes). A canNotCalculateChanges would invalidate my
entire cache.
> Threads/changes created does not contain fake thread
> ----------------------------------------------------
>
> Key: JAMES-3562
> URL: https://issues.apache.org/jira/browse/JAMES-3562
> Project: James Server
> Issue Type: Bug
> Components: JMAP
> Affects Versions: master
> Reporter: Daniel Gultsch
> Assignee: Antoine Duprat
> Priority: Major
>
> I’m doing Email/changes and Thread/changes in the same request.
> The response to Email/changes returns and a newly arrived email id in the
> created list.
> The response to Thread/changes however is empty. With the James’ current
> model of one email one thread I would expect the Thread/changes response to
> inform we of a new thread (that coincidentally has the same ID as the email)
>
> I noticed that Thread/changes did provide me with a new state though. It's
> just that the change itself was completely empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
