This only starts to be noticeable once there are more results than are requested by the Range parameter.
I verified that now we get the latest instead of the oldest results, which make search on e.g. a phone usable.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Feb 28 2024
Feb 28 2024
Feb 21 2024
Feb 21 2024
Feb 20 2024
Feb 20 2024
Feb 19 2024
Feb 19 2024
Feb 5 2024
Feb 5 2024
Feb 2 2024
Feb 2 2024
Feb 1 2024
Feb 1 2024
Jan 31 2024
Jan 31 2024
mollekopf added a reviewer for D4644: Revert email search results by default so we get latest first: Syncroton Developers.
Jan 30 2024
Jan 30 2024
Jan 29 2024
Jan 29 2024
Jan 26 2024
Jan 26 2024
Renamed the member variable
Jan 25 2024
Jan 25 2024
We'll have to double check, but I think the only this we're not sending is the client modifications from the previous sync from the same client.
- Client send modification with synckey=3
- Server responds with synckey=4
- Client sends emtpy sync with synckey=3 (instead of 4)
- Server now responds with synckey=4, but doesn't report the modification again.
mollekopf added a reviewer for D4640: Make sure we always respond with the latest sync key: Syncroton Developers.
Jan 18 2024
Jan 18 2024
This has now been merged into Kolab:16, though the package is still building, but should become available shortly.
Jan 17 2024
Jan 17 2024
Jan 11 2024
Jan 11 2024
Jan 10 2024
Jan 10 2024
Addressed most comments
Jan 9 2024
Jan 9 2024
Adressed most comments, no fruther plans for now
Jan 4 2024
Jan 4 2024
This prevents that we have to replace the config/imap.php file, which works but is slightly annoying because we constantly have a modification in the git repo.
Jan 1 2024
Jan 1 2024