Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I'm trying to improve vGrive performance by changing the mechanism of searching the repository in the web and searching file system multiple times. I think vGrive could do a full search and keep the results locally for imediate references. It would be a kind of cache, where imediate new searches could be made locally in less expensive operations.
I think there are two good alternatives for that. Keeping the records in memory in a HashTable or saving them to a database.
I'd like to try memory option first.
Of course it would be a huge change in system backbone, so I'm trying to go one step at time. This is the first as implementing DriveFile as a class instead of struct. The next is doing a readability refactor in list_files and finally caching things up.
I hope it can be useful.
Thanks.