| Application architecture |
Relies on the WebDAV protocol for cloud storage, which has limitations, including reliability issues, compatibility limitations, and file access problems. |
Marks a significant departure from WebDAV by adopting a highly sophisticated approach to drive mapping that resolves many of the synchronization and compatibility issues inherent in CDM (Legacy). |
| Startup performance |
Drive mapping during startup is slower because WebDAV requires multiple authentication tokens and uses legacy API calls. |
CDM (V3) is faster. Direct drives (drive mapping to OneDrive or specific locations within SharePoint, for example) now map up to twice as fast. Dynamic drives (formerly Converged drives) map five times faster. |
| Synchronization delays |
Due to limitations in the WebDAV protocol, CDM Legacy users often experience delays in synchronization, which can significantly slow down workflows such as opening large folders and files, especially in environments requiring real-time access to cloud-stored files. |
The real-time browse capability in CDM (V3) overcomes such fundamental sync issues. It tracks and syncs changes when you interact with a file or folder. This approach enables CDM to map drives with large volumes of data efficiently. |
| File system limitations |
Due to its reliance on the WebDAV protocol, CDM Legacy has certain file system limitations that concern some of our customers and partners. These include a 260-character file path limit, a 5000-item per folder limit, and a 4GB max upload size limit. |
CDM (V3) has removed all these limitations, although limits imposed by your operating system or cloud storage provider may still apply. |
| Offline behavior |
With WebDAV, connectivity drops cause drives to become unstable, requiring user intervention to restore them. If this happens while you’re trying to save a file in CDM Legacy, it simply fails without retrying. This means you’ll have to try again manually when you’re back online. |
CDM (V3) drives remain responsive without connectivity and can perform specific actions. For example, if a file can’t be uploaded due to connectivity issues, you can still save it, and CDM will wait to upload it automatically as soon as the connection is restored. |
| Throttling management |
With WebDAV, throttling in CDM Legacy can cause drive failures, failed uploads, or empty folders when browsing. Additionally, WebDAV finds it challenging to cope with throttling, as it continues sending requests, which can increase throttling, until the connection slows to the point of failure. |
CDM (V3) is significantly better at dealing with API throttling. When it receives throttle warnings, it responds efficiently, reducing the possibility of further escalation. For more information about throttling and how the CDM (V3) architecture is substantially better than CDM Legacy in reducing the likelihood of throttling, see Throttling. |
| Authentication |
CDM (Legacy) authenticates twice. Once to Microsoft Graph and once for WebDAV. |
CDM (V3) simplifies the authentication process and completely avoids a range of problems related to WebDAV cookies. |
