Switch rooms directly without explicitly leaving old and joining new.
Open
Nobody has claimed this yet.
feature: federation 🌐
feature: frontend 🖌️
feature: signaling 📶
performance 🚀
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
One possible optimization:
- When switching rooms, clients should not leave the room before joining the new one. Currently clients send a
roomrequest with an empty room id (which leaves the current room) and then anotherroomrequest with the new federated room. Switching directly would allow to reuse the federated connection.
Originally posted by @fancycode in https://github.com/nextcloud/spreed/issues/12604#issuecomment-2236749121
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
No files or tests are named. Start by tracing the client room-switching flow and the room request handling described in the issue, then identify how federated connections are reused. Done means switching rooms no longer sends a separate leave request before joining the new federated room, with existing room-switching behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100