Design Correction to Prioritize Cloud Storage in Multi User Environments
Clearly manipulating files directly from the cloud is the only and most efficient usage when working in multi user environments.
This is evidenced by office directly connecting and prioritizing OD and ODfB over local storage.
Complexity occurs when dealing with offline files, in particular, versioning issues. In normal server/multi user environments first access RW and second acces RO are the common and most useful mechanism to deal with this issue. Databases of course deal with file, record and of course field locking.
OD and ODfB need a couple of fundamental changes in order for it to really work well in cloud only multi user environments. Office 365 / Azure, Windows Users.
This applies to Windows Clients only, the other platforms become derivatives of this.
Windows File Explorer is a key component and should have the ability to directly connect to OD and ODfB. All file based functions normally used should work 'naturally.. Unlike today's implementation that either requires the local sync client or a web part connection which are completely ineffective. To be clear when file operations occur through File Explorer they are commands sent to the server (client/server) and therefore process on Azure not via the local connection and Azure. Only results are displayed 'locally'. This singular and missing capability renders this environment useless.
Admin level control in order to define permissions, access, RO vs. RW for first and second concurrent access to the same file.
The browser version of the folder / data structure interface should mimic in both look/feel and function that of Windows File Explorer. Capabilities here being the key.
Versioning, check in/check out, multi user editing, change logs by editor by time/history sequentially with views to clearly show the evolution of a document.
This component now has to do with offline files which create the complexity of having different versions of the same file and the ultimate significant issue for IT and the user community.
Do not use a sync client that is installed on a local users profike which requires a cryptic profile based custom directory structure... OneDrive or company-ODfB. This custom and dedicated file structure is a bolt on and is unnecessary. The built in Offline Folders function of Windows should own this component. It is built in and you can choose any storage areas you wish to sync. Here is where local user data would be selected and then corporate repositories think common shared data...
When connected to the internet cloud priiritization for opening files and RW for first access and RO for second acces should be the default configuration.
Placeholder files if this can be done with any technical success
Delta change for file syncing. The ability to only sync the part of the file that has changed would seem obvious exists in the current server DFS implementations but curiously was omitted by a product being used by millions with huge amounts of data.
Check out capabilities again to assist in the prevention of versioning issues
API for third party software and platforms to have the same direct access.
If the above was done then moving to the cloud for business and multi user environments would become a reality l. It is the aforementioned BASIC file, sharing and permission requirements which must exist for multi user environments to work. Unless everything becomes web based and local machines still exist this is required.