3rd party API: speed up synchronization

[nextcloud]

3rd party API: speed up synchronization

[korelstar]

@nextcloud/notes
Please have a look at my reference implementation and the discussion over there: #51.

[spaetz]

I am not sure, why you choose such a difficult approach. Using the if-modified-since header, a client could choose to only receive notes that were changed since the last check.
https://developer.mozilla.org/de/docs/Web/HTTP/Headers/If-Modified-Since

Why would you not use something like this, then the total number of notes does not matter (as most will not have changed betwen syncs) and you are not limited to a maximum of 400 notes in total which will come and bite you at some point in time.

[korelstar]

The main problem was, that Nextcloud doesn't maintain the "real" last modified time of a note. Please see #51 for a discussion about this problem.

However, based on that discussion, I went another way. With the realization in #95, we are not limited to a certain number of notes. Nevertheless, if you have any ideas how to improve that implementation, I would be very happy to discuss those.

But please note, that the description in this issue is totally outdated and doesn't correspond to the current implementation. Therefore, I'm closing this issue since it is solved by #95 (only the API documentation has to be extended in this aspect).