A comparison of view features
A comparison of view features between dynamic views and snapshot views.
Feature | For dynamic views | For snapshot views |
---|---|---|
Storage requirements | You need enough disk space to store any view-private files or view-private directories. | You need enough disk space to store the copies of the loaded elements and any view-private files or view-private directories. |
To access HCL VersionVault elements | You start the view and mount VOBs on your computer | The config spec for your view loads elements into the view. |
Assigning views to drives (Windows® systems only) | You can start a view and assign it to a drive at the same time. | Because you do not start a snapshot view, you must assign the view to a drive to access it from Windows® Explorer. |
Version selection | For any element in a mounted VOB, the view always selects the version specified by the config spec. You can traverse the view-extended namespace to see any version of any element in any mounted VOB. | You use the update command to update the elements loaded into the view. You can see only the version of an element that is loaded into your view. |
VOB symbolic links and VOB hard links (Windows® system treatment only) | The link is traversed each time you access the object. | The version to which the link resolves at update time is copied into the view. |
Version that is checked out | By default, the checkout operation checks out the latest version on a branch, regardless of what the config spec specifies. | The checkout operation checks out the file loaded in your view, which may not be the latest version on a branch. |
Build features | You can use the clearmake (and omake on Windows® computers) features of build auditing and build avoidance. | You can use clearmake (or omake on Windows® computers), but the build auditing and build avoidance features are disabled. |
Sharing the views with other team members | View objects are accessible to other team members through the HCL VersionVault view-extended namespace. | View objects are accessible to other team members if you make the root directory of the view a shared folder in the Windows® file system. Snapshot views are not accessible through the HCL VersionVault view-extended namespace. |