shared repository workspace
![]()
Bernd van Oostrum (217●3●56●73)
| asked Aug 22 '17, 4:10 a.m.
edited Aug 23 '17, 11:05 p.m. by David Lafreniere (4.8k●7) Hi,
Is it discouraged to use a shared repository workspace for different clients? Let's say I want to use that workspace from both Windows Shell (for documents) and IDz.
Regards,
Bernd.
|
Accepted answer
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Aug 22 '17, 4:35 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Aug 22 '17, 4:56 a.m. You should never use a shared repo workspace for anything. A repository workspace must only ever be loaded by the user once. Concurrently working on the same components in the same repository workspace from different clients causes the repository workspace to go out of sync.
Bernd van Oostrum selected this answer as the correct answer
Comments What is the reason behind this limitation? It seems using different clients corrupts the metadata...
Thanks a lot for the confirmation, Ralph.
1
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
No, streams are used to allow concurrent changes in components in the repository workspaces that flow to them. Although a repository workspace behaves almost as a stream it assumes changes either being done by a user and checked in or changes flow from streams.
1
![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The limitation is for improving performance. If each sandbox for a given repository workspace kept track of all the information needed to efficiently deal with that repository workspace being modified by another client, then there would be a significant performance cost. Instead, the sandbox implementation is optimized to assume it is very infrequent that some other client will modify that repository workspace (but it will notice, and then perform a usually expensive reconcile operation). If the metadata is corrupted, that is a bug, and preferably you would report it so that it can be fixed (i.e. a sandbox will go out of sync if the workspace is modified by another client, but the metadata should not be corrupted). |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.