A workspace is an area where you can view or modify components.
A repository workspace on the server stores components as versionable artifacts
that can be loaded into a local workspace (such as an Eclipse workspace or
an ordinary folder) on the client.
A repository workspace is a repository object that stores items
that have been placed under source control. Every repository workspace has
an owner, and only the owner can make changes in the workspace. The configuration
of a workspace, defined by the change sets it contains, can be modified, saved,
and restored using workspace tools. Changes you make to items in your workspace
remain private to the workspace until you decide to share them by delivering
them to a workspace flow target. When you want to work with changes that other
users have made in their repository workspaces, you can accept them into your
workspace.
Note: Workspaces in which none of the work is shared with other
users have no flow targets, and cannot deliver or accept changes.
Repository workspaces and local workspaces
Repository workspaces are objects in the repository. Local workspaces are directories in your computer's file system.
In the repository, files and folders are stored as versionable items whose data and metadata can be viewed but not directly modified. To enable integration with file-based tools such as editors, compilers, and debuggers, files and folders in a repository workspace are loaded (copied) into a local workspace on your computer. As you make changes to files and folders in the local workspace, you periodically check them in, which copies the changes to the repository workspace. When all the changes in your local workspace are checked in, the repository and local workspaces have the same content.
Figure 1 illustrates
a simple configuration of a repository workspace a single component. Check-in
copies changes from the local workspace to the repository workspace. Load
loads the local workspace with the contents of the repository workspace.
