User Guide - MKS

Chapter 2: Understanding Source Integrity
16
The history for an object with its versions.
How Files and Objects Are Stored
Source Integrity stores your development files and Web objects in projects
and archives, and then manages access to them through sandboxes.
The data preserved in Source Integrity histories can be one of two types,
Binary or Text. Binary is a file containing unprintable characters, or lines
too long to be handled by text editors. Text is the file format expected by
MS-DOS and Windows text file editors. When a file of type “Text” is
checked out, Source Integrity adds the appropriate line ending character
for that type of client.
An archive is a file containing the history of a member (a record of all the
changes made to it since it was put under revision control). From the
information contained in the history, Source Integrity can reconstruct any
previous version of the member. The archive is sometimes referred to as
the RCS file, for historical reasons.
This procedure has a number of advantages over other software
configuration management systems in that it:
simplifies the identification and retrieval of earlier versions of
development objects
provides control over access to data files
keeps team members well informed on project status
u s e r g u i d e