Page History
...
Consider the following scenarios involving three developers:
Scenario 1
John, Bob and Mary each have their own Visual LANSA PC workstation. Each PC is defined as a repository group, i.e. there are three repository groups defined. No work groups are defined. Whenever John, Bob or Mary checks-in a change to LANSA for i, the change is propagated to all developer PCs using repository synchronization.
Scenario 2
Work Group 1 |
|---|
Bob |
Mary |
Bob and Mary are working on the same application. When Bob checks-in his new objects to LANSA for ifor i, Mary needs to know about these changes, but not John. A work group is created for Bob and Mary to keep their repositories synchronized. John is not part of this work group. When John checks-in his changes, repository synchronization will not update Bob or Mary.
Scenario 3
Work Group 1 | Work Group 2 |
|---|---|
Bob | John |
Mary | Bob |
John and Bob have created a second work group. When John checks-in his changes, they are sent to Bob but not to Mary. Likewise, Mary's changes are sent only to Bob. Because Bob is part of both work groups, his changes are sent to both Mary and John.
Also Also See
6.3.1 Repository Synchronization Concepts
...