Interesting development here, this is certainly a good idea to throw. I feel an urge to participate into the discussion because in our company NC is a key piece of some applications and if not suitable the VirtualDrive evolution might break the whole process.
Same things, different perspective
I have not seen in the debate the remark that in some sense the functions provided by the client with the VD are not fundamentally different: both allow local access to NC-stored data, both allow a local copy when the system is offline, both allow the sync thread to run automatically.
In that sense I view it as an important but incremental evolution (which is good to me).
The fact that the local replica becomes a “second grade” storage (from real volume to cache) is definitely a warning signal. And I have to learn what Doken can do. Let’s study!
Talking about customer scenario, let me try to make a simple but complete list of what we would need from any sync mechanism, first with a must-have list
- local copy of data
- access to the local copy for local process to write (local applications create new files and directories all the time)
- possibility to leave a local cache copy even if it is not synced (and would be synced for instance one month later)
- possibility to remotely delete local cache files (deleted on the server, deletion replicated on the client and client’s cache)
- better mechanism to handle merge conflicts or places where contradictions appear. Currently I have github issue 998 open which needs extra workaround procedures.
- security and access handling to determine which data a user might potentially see (through sharing I guess)
And a nice-to-have list
- possibility to tune the cache retention period by directory
- efficient synchronisation in terms of speed, local memory and cpu consumption (current client is ok but not great)
- functions to avoid conflicts in the mapped drive letter
Of course this is food for thought into the debate, so feel free to pick . I will continue to participate into the interesting discussion.
Thanks a lot for the hard work, NC is a great tool and has made giant steps.