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

adjust LSP storage scheme to be usable by multiple instances simultaneously #344

Open
GitMensch opened this issue Aug 6, 2024 · 0 comments
Labels
lsp-server Specific to the LSP server next β release

Comments

@GitMensch
Copy link
Contributor

the only remaining option is to store the cache in a shared location (like in the project itself) and access it via multiple LSP servers. At the moment that's not supported (the cache itself is a single file that's juste blindly read on LSP server startup and written on shutdown), but I think moving towards a different storage scheme for the cache would not be too complicated.

Originally posted by @nberth in #343 (comment)

So this issue is about a possible adjustment. And yes, for bitlang.cobol (an older version where this was possible) we use the setup of a cache directory below the project (outside of the directories from the workspace as there's no use in indexing it). Note: that extension has an explicit command to index the whole workspace (and another to check for necessary updates on startup) which allows fast LSP access later (the cache entries are updated on file writes and are then available for anyone directly).

@nberth nberth added this to the First β release milestone Aug 7, 2024
@nberth nberth added next β release lsp-server Specific to the LSP server labels Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lsp-server Specific to the LSP server next β release
Projects
None yet
Development

No branches or pull requests

2 participants