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

find a better way to cache objects between main and ext host #11455

Closed
jrieken opened this issue Sep 2, 2016 · 0 comments · Fixed by #11583
Closed

find a better way to cache objects between main and ext host #11455

jrieken opened this issue Sep 2, 2016 · 0 comments · Fixed by #11583
Assignees
Labels
debt Code quality issues

Comments

@jrieken
Copy link
Member

jrieken commented Sep 2, 2016

In the extension host we often cache objects for a certain period of time. For instance those are command arguments, completion items and code lenses that need resolving, code action etc. We employ some sketchy mechanism to cache and clear them - mostly as long until the next request comes in. That has issues if you make requests if you make request in parallel and needs for a better solution

@jrieken jrieken added the debt Code quality issues label Sep 2, 2016
@jrieken jrieken self-assigned this Sep 2, 2016
@jrieken jrieken added this to the September 2016 milestone Sep 2, 2016
@jrieken jrieken mentioned this issue Sep 7, 2016
@egamma egamma reopened this Sep 8, 2016
jrieken added a commit that referenced this issue Sep 19, 2016
@jrieken jrieken closed this as completed Sep 23, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debt Code quality issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants