Improve polling interval for read only sessions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
With https://github.com/nextcloud/text/pull/5930 reducing the polling interval we should improve this further in the future.
My current idea is to add the read only state of a session to the db so that the frontend can actually check if there are other users in a document that could change the content. If there are we can do the regular polling interval, otherwise we can stay at 30s or even further reduce it.
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
Start by tracing the existing frontend polling behavior and how session state is persisted in the database. Define how read-only status and the presence of other users should affect the polling interval, then verify that active documents poll regularly while inactive read-only sessions can use a longer interval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- database, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100