Reduce polling time on read only public shares
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
Polling intervals that trigger the sync requests are quite frequent. We should reduce the polling internal in cases where immediate updates may not be that relevant:
- When a user is the only one in a document
- For read only sessions (maybe even higher intervals when no people with editing rights are in the document)
Relevant code parts:
https://github.com/nextcloud/text/blob/ea17f697135e1e274673b4c2523004a8d7e3def2/src/services/PollingBackend.js#L31-L53
On the way doing this the logic could also be refactored a bit to be easier to understand
Assigning performance tag and enhancement since this would help reduce the server load.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read src/services/PollingBackend.js around lines 31-53 first, then trace how participant presence and read-only or editing permissions are exposed to the polling logic. Done means polling intervals are reduced for solo and read-only sessions, with the behavior clearly covered by the existing relevant checks or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100