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

In-memory or fs-based cache files abstraction #219

Closed
meriadec opened this issue Mar 7, 2018 · 0 comments
Closed

In-memory or fs-based cache files abstraction #219

meriadec opened this issue Mar 7, 2018 · 0 comments
Labels
next

Comments

@meriadec
Copy link
Contributor

meriadec commented Mar 7, 2018

Following discussions in #172, saving file to disk at each change can lead to problems and incomprehensions on the user side.

The app should be able to use a memory copy of the edited file to allow user to save/discard changes, and prevent unnecessary accesses to file-system.
@meriadec meriadec added the next label Mar 7, 2018
This was referenced Mar 7, 2018
Closed
Closed
Closed
@meriadec meriadec added this to the 2.9.0 milestone Mar 7, 2018
@meriadec meriadec removed this from the 2.9.0 milestone Apr 5, 2018
@meriadec meriadec mentioned this issue Aug 28, 2018
Closed
@kmcb777 kmcb777 mentioned this issue May 22, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
next
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@meriadec