Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove workspace id from websocket connection path to master #1787

Closed
vparfonov opened this issue Jul 18, 2016 · 1 comment
Closed

Remove workspace id from websocket connection path to master #1787

vparfonov opened this issue Jul 18, 2016 · 1 comment
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Milestone

Comments

@vparfonov
Copy link
Contributor

Workspace statuses are now tracked by various websocket connections per workspace id. It creates a lot of problems in order to handle the high number of websockets. (especially in dashboard)
Providing one connection with various channels will decrease the number of persistent websocket connections. Thus the clients will be able to use one connection to listen statuses of all workspaces, instead on multiple ones.

@vparfonov vparfonov added kind/task Internal things, technical debt, and to-do tasks to be performed. sprint/next team/ide labels Jul 18, 2016
@vparfonov vparfonov added this to the 4.6.0 milestone Jul 18, 2016
@TylerJewell
Copy link

@vparfonov - is there a PR for this? Why add to 4.6 milestone if PR is not readied.

@vparfonov vparfonov removed this from the 4.6.0 milestone Jul 21, 2016
@vkuznyetsov vkuznyetsov added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/enterprise and removed team/ide labels Aug 30, 2016
@vinokurig vinokurig added status/in-progress This issue has been taken by an engineer and is under active development. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. status/in-progress This issue has been taken by an engineer and is under active development. labels Oct 18, 2016
@vinokurig vinokurig added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Oct 25, 2016
@vinokurig vinokurig added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Oct 27, 2016
@vinokurig vinokurig removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Oct 31, 2016
@bmicklea bmicklea added this to the 5.0.0-M7 milestone Nov 4, 2016
@bmicklea bmicklea mentioned this issue Nov 16, 2016
66 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

No branches or pull requests

5 participants