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.

Sign up for GitHub

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

Jump to bottom

subscription event handling #24

Open
2 of 3 tasks
snvfk1n opened this issue Nov 19, 2019 · 0 comments
Open
2 of 3 tasks

subscription event handling #24

snvfk1n opened this issue Nov 19, 2019 · 0 comments
Assignees
@snvfk1n

Comments

@snvfk1n
Copy link
Member

snvfk1n commented Nov 19, 2019 •
edited
Loading

right now, we push the whole document state to subscribers when changes occur. this, however, can lead to bottlenecks especially when considering the WS bridge and gateway in the gateway process.

  • make change requests transmit their responses before sending out subscriber pushes
  • try out hash-based diffing for watch handlers and sparsely transmit changes to subscribers
  • debounce watch calls?
@snvfk1n snvfk1n self-assigned this Nov 19, 2019
@snvfk1n snvfk1n changed the title make pub/sub data pushes sparse subscription event handling Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@snvfk1n snvfk1n

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@snvfk1n