About VersionVault views

An HCL VersionVault view provides access to resources in HCL VersionVault repositories.

Before you can access resources stored in an HCL VersionVault repository (VOB) or add existing resources to VersionVault source control, you must create an HCL VersionVault view. A VersionVault view selects a specific set of file and directory versions from one or more VOBs so that you can access them on your computer.

Types of VersionVault views

The HCL VersionVault Explorer for VersionVault Express supports the following types of view:

  • Automatic views
  • Web views
The automatic view is a type of WAN-friendly view that combines aspects of the web view. It is distinguished from other view types by the following characteristics:
  • Instant workspace creation - Automatic views enable you to start using the workspace immediately, without waiting for it to be populated with any files.
  • Per-view VOB mounts - Mounting a VOB in an automatic view immediately makes the version-controlled files in that VOB available in the view. VOBs mounted for an automatic view are managed separately for each automatic view. Thus, a set of VOBs mounted in one automatic view can be a different set from those mounted for another automatic view on the same system.
  • Shared cache - All of your automatic views on a machine typically share a common cache of version-controlled files: the shared cleartext cache. If one view has fetched a file, all of the other automatic views that were created by the same user on the same machine simply access the cache to obtain that file.
  • Prefetching - Although automatic views fetch files when they are first needed (that is, on demand), accessing a file that is already locally cached is orders of magnitude faster than waiting for the file to be fetched from a remote VOB. In addition to the shared cleartext cache, there are a couple of other mechanisms that automatic views use to increase the odds that a file will be cached before you actually need it. One mechanism is load rules, a feature that automatic views share with web views. Load rules are not required for automatic views when you work online, but they can improve performance by pre-fetching version-controlled files that you might need. You can also use load rules to fetch the files that you need before disconnecting from the VersionVault WAN server.
  • "Frozen time" mode - Although automatic views can fetch version-controlled files on-demand (when they are first accessed), they "freeze" time when the view is created or updated. If you update an automatic view at 9:00 AM on 16-July but do not access "mycode.c" until 11:00 AM, you'll see the latest version of "mycode.c" as of 9:00 AM, even if someone else checked in a successor version at 10:00 AM from a different view. To show the changes that were made after 9:00 AM 16-July, you would update your view.
  • Instant view updates - You can use an automatic view immediately after starting a view update operation. The view ensures that the correct version of any file is available even if the view update operation has not yet completed.

A web view is a copy-based VersionVault view that is tolerant of high-latency connections to a VersionVault WAN server, although it might be used in both wide-area network (WAN) and local area network (LAN) environments.

Modifying files in a VersionVault web view

Modifying files in a web view means that VersionVault WAN server serves as an intermediary between the web view and the VOB server.

Modifying files in a VersionVault automatic view

Modifying files in an automatic view is similar to modifying files in a web view: you can check out files while you are connected to the VersionVault WAN server, or hijack them.

For more information about automatic views, see the documentation for VersionVault.
Note: See About the documentation to be aware of the distinctions for the documentation for HCL VersionVault Express versus the documentation for HCL VersionVault.