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

Pipelining for incremental diagram generation #194

Open
Eddykasp opened this issue Apr 17, 2024 · 0 comments
Open

Pipelining for incremental diagram generation #194

Eddykasp opened this issue Apr 17, 2024 · 0 comments
Labels
enhancement New feature or request LSP Affect the klighd language server. requires client change This change is linked to some change on the client side implementation in klighd-vscode

Comments

@Eddykasp
Copy link
Contributor

Pipelining the requests could potentially reduce the total transmission time significantly when using the incremental diagram generation. Since the exact order in which pieces should be sent is not clear and may change dynamically as the user interacts with the partially loaded diagram, the details of how to manage the priority of requests (and potentially cancel requests) should be considered.
@Eddykasp Eddykasp added enhancement New feature or request LSP Affect the klighd language server. requires client change This change is linked to some change on the client side implementation in klighd-vscode labels Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request LSP Affect the klighd language server. requires client change This change is linked to some change on the client side implementation in klighd-vscode
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Eddykasp