It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,844

question asked: Feb 10 '11, 9:02 p.m.
question was seen: 5,921 times
last updated: Feb 10 '11, 9:02 p.m.

Related questions

It sounds expensive to have streams and repository workspace

0
Jirong Hu (1.5k●9●295●258) | asked Feb 10 '11, 9:02 p.m.
Hi

I found the following in Jazz FAQ. Sounds like version control system only stores the delta. What I don`t understand is what`s this pointer points to? Does it mean, the local workspace is not fully loaded with actually files (but I do see the files are local)?

e.g. If I create three personal workspace locally, what are these workspace points to?

Thanks
Jirong

It sounds expensive to have streams and repository workspaces keep copies of all files?
In some documents about Jazz Source Control it sounds like each repository workspace and stream has a complete copy of all the files and folders in the repository. This is an oversimplification. Under the covers histories are shared and when creating a repository workspace from a stream, only the pointer to the stream's history needs to be referenced. Then as new change sets are created in the repository workspace they are appended to a new history owned by the workspace.

6 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Michael Valenta (3.7k●3) | answered Feb 11 '11, 9:31 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
The file and folder items are shared between workspaces and streams. As a workspace diverges from a stream, there will be some data that is associated only with that workspace but this is stored in a delta form so that each workspace does not have a complete copy of all the data.
0
permanent link
Jirong Hu (1.5k●9●295●258) | answered Feb 11 '11, 9:39 a.m.
The file and folder items are shared between workspaces and streams. As a workspace diverges from a stream, there will be some data that is associated only with that workspace but this is stored in a delta form so that each workspace does not have a complete copy of all the data.


Still not clear. Can you explain to me the stream, repository workspace and local workspace? Let me guess:
1. Stream is shared.
2. Every one creates repository workspace for himself, load things from the stream? This is where the repository delta comes from.
3. Everyone has a local workspace, a load loads files from his repository workspace to local workspace?
4. A check-in moves files from local workspace to repository workspace? A deliver moves files from repository workspace to stream?
5. What we see files in our local PC are local workspace, they are real files and what people concern about the disk space. This is like a snapshot view.

I have years of experience in CC.

Thanks
Jirong
0
permanent link
Christophe Cornu (471●2●3) | answered Feb 11 '11, 8:58 p.m.
Hi:

Here's a good read: "How scalable are repository workspaces?"
http://jazz.net/blog/index.php/2009/03/23/how-scalable-are-repository-workspaces/

HTH,
Christophe Cornu
RTC SCM Client
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Feb 15 '11, 12:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, all of that is correct, but the term "local workspace" has been
deprecated ... the file area on your local machine where the files under
version control are loaded is called a "sandbox".

And yes, all of those statements about "sharing" and "pointers" are
talking about the "repository workspace" (an object on the server), and
not the "sandbox" (the file area which contains copies of the
version-controlled files).

The main reason we deprecated the phrase "local workspace" was to avoid
this kind of confusion about what a "workspace" referred to.

Cheers,
Geoff

On 2/11/2011 9:53 AM, hujirong wrote:
mvalentawrote:
The file and folder items are shared between workspaces and streams.
As a workspace diverges from a stream, there will be some data that
is associated only with that workspace but this is stored in a delta
form so that each workspace does not have a complete copy of all the
data.

Still not clear. Can you explain to me the stream, repository
workspace and local workspace? Let me guess:
1. Stream is shared.
2. Every one creates repository workspace for himself, load things
from the stream? This is where the repository delta comes from.
3. Everyone has a local workspace, a load loads files from his
repository workspace to local workspace?
4. A check-in moves files from local workspace to repository
workspace? A deliver moves files from repository workspace to
stream?
5. What we see files in our local PC are local workspace, they are
real files and what people concern about the disk space. This is like
a snapshot view.

I have years of experience in CC.

Thanks
Jirong
0
permanent link
Lilach Eisenberg (31●3●2) | answered Feb 17 '11, 12:59 a.m.
Is it accurate to say that the repository workspace is equivalent to a development stream and the sandbox is equivalent to view? what is the difference between repository workspace and local workspace?
If the first assumption is correct, the best practice should be to load one repository workspace per sandbox?
Yes, all of that is correct, but the term "local workspace" has been
deprecated ... the file area on your local machine where the files under
version control are loaded is called a "sandbox".

And yes, all of those statements about "sharing" and "pointers" are
talking about the "repository workspace" (an object on the server), and
not the "sandbox" (the file area which contains copies of the
version-controlled files).

The main reason we deprecated the phrase "local workspace" was to avoid
this kind of confusion about what a "workspace" referred to.

Cheers,
Geoff

On 2/11/2011 9:53 AM, hujirong wrote:
mvalentawrote:
The file and folder items are shared between workspaces and streams.
As a workspace diverges from a stream, there will be some data that
is associated only with that workspace but this is stored in a delta
form so that each workspace does not have a complete copy of all the
data.

Still not clear. Can you explain to me the stream, repository
workspace and local workspace? Let me guess:
1. Stream is shared.
2. Every one creates repository workspace for himself, load things
from the stream? This is where the repository delta comes from.
3. Everyone has a local workspace, a load loads files from his
repository workspace to local workspace?
4. A check-in moves files from local workspace to repository
workspace? A deliver moves files from repository workspace to
stream?
5. What we see files in our local PC are local workspace, they are
real files and what people concern about the disk space. This is like
a snapshot view.

I have years of experience in CC.

Thanks
Jirong
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Feb 18 '11, 1:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Not sure what you mean by a "local repository" ... I'll assume you meant
a "repository workspace". That is similar to (but not equivalent to) a
ClearCase development stream.

And you have to define both a repository workspace and a sandbox for the
same reason that in ClearCase, you have to define both a development
stream and a snapshot view.

Cheers,
Geoff

On 2/17/2011 1:08 AM, lilache wrote:
If the local repository is equivalent to a development stream and the
sandbox (which actually holds the local copies of the files) is
equivalent to a snapshot view - What does "workspace"
stands for? why do I have to define both WS and sandbox?

gmclemmwrote:
Yes, all of that is correct, but the term "local workspace"
has been
deprecated ... the file area on your local machine where the files
under
version control are loaded is called a "sandbox".

And yes, all of those statements about "sharing" and
"pointers" are
talking about the "repository workspace" (an object on the
server), and
not the "sandbox" (the file area which contains copies of
the
version-controlled files).

The main reason we deprecated the phrase "local workspace"
was to avoid
this kind of confusion about what a "workspace" referred
to.

Cheers,
Geoff

On 2/11/2011 9:53 AM, hujirong wrote:
mvalentawrote:
The file and folder items are shared between workspaces and
streams.
As a workspace diverges from a stream, there will be some data that
is associated only with that workspace but this is stored in a
delta
form so that each workspace does not have a complete copy of all
the
data.

Still not clear. Can you explain to me the stream, repository
workspace and local workspace? Let me guess:
1. Stream is shared.
2. Every one creates repository workspace for himself, load things
from the stream? This is where the repository delta comes from.
3. Everyone has a local workspace, a load loads files from his
repository workspace to local workspace?
4. A check-in moves files from local workspace to repository
workspace? A deliver moves files from repository workspace to
stream?
5. What we see files in our local PC are local workspace, they are
real files and what people concern about the disk space. This is
like
a snapshot view.

I have years of experience in CC.

Thanks
Jirong

Your answer

Register or to post 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.