Hi,
Our team works with RTC for serveral months, we always meet component out of sync issue.

The situation is like that: we have many streams including many components, we create one workspace for each stream, and specially we work with two or more computers, each computer installs RTC also. Then the question comes, we deliver some changes from a computer, and then we use another computer, we can find that it shows the same component is out of sync , in order to fix the issue we have to replace with the latest from the stream, that means it will download the entire component to local...

I know we have a workround way to aviod the issue: create different workspace on different computer for the same stream.But we have many streams, we don't want to add more workspaces...

Does RTC team have any idea to avoid this issue? I think the best way is one workspace can run on every host! The good way is keep out of sync status and load only the changes, not the entire component, that is reasonable!

Thoughts?

saphenwrote:
Hi,
Our team works with RTC for serveral months, we always meet
component out of sync issue.

The situation is like that: we have many streams including many
components, we create one workspace for each stream, and specially we
work with two or more computers, each computer installs RTC also. Then
the question comes, we deliver some changes from a computer, and then
we use another computer, we can find that it shows the same component
is out of sync , in order to fix the issue we have to replace with
the latest from the stream, that means it will download the entire
component to local...

I know we have a workround way to aviod the issue: create different
workspace on different computer for the same stream.But we have many
streams, we don't want to add more workspaces...

Does RTC team have any idea to avoid this issue? I think the best
way is one workspace can run on every host! The good way is keep out
of sync status and load only the changes, not the entire component,
that is reasonable!

Thoughts?

Hi,

Basically Each user is supposed to have his own repository workspace.
The stream is the thing for sharing. The Repository workspace you are
not supposed to work against in parallel. Each Repository workspace
flowing against a stream gets information about potential incoming
and outgoing changes and can deliver/accept if convenient.

Using RTC 3.0 iFix1, I opened a Word document from my sandbox using "Open With" to launch Word in a separate window.

After I saved my changes, I was surprised that the file did not appear in the "Pending Changes" view.

It works fine if I open the document in an Eclipse view, but I lose access to some of the Word functionality.

Is there a way to fix this behaviour, other than using Refresh?

That is not come from document, maybe it's our habit...
Every person in our team has a laptop and a desktop, we always change to use, and also we maybe use the desktop via VPN at home, so we install RTC onto the two machines.
From a RTC newer habit, we just create a new workspace for a stream on a machine at the beginning, when we use another machine to connect to JAZZ server with RTC we can get the workspace we just created. So we will load the the same workspace on each machine, so that the issue may come out.
I think it is the habit of each RTC newer which use more than one machine at the same time. And they will meet the issue as I did.

Yep, creating a workspace is a minimal footprint, but if we have many streams/components, the workspaces' number will be double because we have two machines... I think less workspace will lead to be found out easily and fetched quickly from remote jazz server.

That is not come from document, maybe it's our habit...
Every person in our team has a laptop and a desktop, we always change
to use, and also we maybe use the desktop via VPN at home, so we
install RTC onto the two machines.
From a RTC newer habit, we just create a new workspace for a stream on
a machine at the beginning, when we use another machine to connect to
JAZZ server with RTC we can get the workspace we just created. So we
will load the the same workspace on each machine, so that the issue
may come out.
I think it is the habit of each RTC newer which use more than one
machine at the same time. And they will meet the issue as I did.

Yep, creating a workspace is a minimal footprint, but if we have many
streams/components, the workspaces' number will be double because we
have two machines... I think less workspace will lead to be found out
easily and fetched quickly from remote jazz server.

gmclemmwrote:
+1 for Ralph's response.

Just for interest's sake, what made you think that it was a good
idea
(or necessary) to share a workspace between multiple people or
multiple
machines? If it was from the RTC documentation, we will get that
fixed.

Cheers,
Geoff

On 6/22/2011 12:08 PM, rschoon wrote:
saphenwrote:
Hi,
Our team works with RTC for serveral months, we always meet
component out of sync issue.

The situation is like that: we have many streams including many
components, we create one workspace for each stream, and specially
we
work with two or more computers, each computer installs RTC also.
Then
the question comes, we deliver some changes from a computer, and
then
we use another computer, we can find that it shows the same
component
is out of sync , in order to fix the issue we have to replace with
the latest from the stream, that means it will download the entire
component to local...

I know we have a workround way to aviod the issue: create different
workspace on different computer for the same stream.But we have
many
streams, we don't want to add more workspaces...

Does RTC team have any idea to avoid this issue? I think the best
way is one workspace can run on every host! The good way is keep
out
of sync status and load only the changes, not the entire component,
that is reasonable!

Thoughts?

Hi,

Basically Each user is supposed to have his own repository
workspace.
The stream is the thing for sharing. The Repository workspace you
are
not supposed to work against in parallel. Each Repository workspace
flowing against a stream gets information about potential incoming
and outgoing changes and can deliver/accept if convenient.

I don't know why you insist on the old mechanism about workspace and single file area.
From my sight, it would be good way to not loading entire component after the status is "out of sync", just load the changes. Like the command of "accept" which accepts remote repository's changes, can I use the "accept" command to accept the changes I make also?

Finding a workspace on the server is trivial and fast (those tables are
all indexed).

To understand why it is essential to have a workspace associated with a
single file area, logically, RTC keeps information about the
relationship between a single file area and a workspace. While you
update that file area with that workspace, everything is incremental and
fast. If you try to load a different file area from that workspace, RTC
has to scan the contents of that file area to see how it corresponds to
that workspace. So you never want to switch the file area that is
loaded from a given workspace, because you will pay the cost of that
"synchronization".

Cheers,
Geoff



On 6/23/2011 10:38 AM, saphen wrote:

That is not come from document, maybe it's our habit...
Every person in our team has a laptop and a desktop, we always change
to use, and also we maybe use the desktop via VPN at home, so we
install RTC onto the two machines.
From a RTC newer habit, we just create a new workspace for a stream on
a machine at the beginning, when we use another machine to connect to
JAZZ server with RTC we can get the workspace we just created. So we
will load the the same workspace on each machine, so that the issue
may come out.
I think it is the habit of each RTC newer which use more than one
machine at the same time. And they will meet the issue as I did.

Yep, creating a workspace is a minimal footprint, but if we have many
streams/components, the workspaces' number will be double because we
have two machines... I think less workspace will lead to be found out
easily and fetched quickly from remote jazz server.

gmclemmwrote:
+1 for Ralph's response.

Just for interest's sake, what made you think that it was a good
idea
(or necessary) to share a workspace between multiple people or
multiple
machines? If it was from the RTC documentation, we will get that
fixed.

Cheers,
Geoff

On 6/22/2011 12:08 PM, rschoon wrote:
saphenwrote:
Hi,
Our team works with RTC for serveral months, we always meet
component out of sync issue.

The situation is like that: we have many streams including many
components, we create one workspace for each stream, and specially
we
work with two or more computers, each computer installs RTC also.
Then
the question comes, we deliver some changes from a computer, and
then
we use another computer, we can find that it shows the same
component
is out of sync , in order to fix the issue we have to replace with
the latest from the stream, that means it will download the entire
component to local...

I know we have a workround way to aviod the issue: create different
workspace on different computer for the same stream.But we have
many
streams, we don't want to add more workspaces...

Does RTC team have any idea to avoid this issue? I think the best
way is one workspace can run on every host! The good way is keep
out
of sync status and load only the changes, not the entire component,
that is reasonable!

Thoughts?

Hi,

Basically Each user is supposed to have his own repository
workspace.
The stream is the thing for sharing. The Repository workspace you
are
not supposed to work against in parallel. Each Repository workspace
flowing against a stream gets information about potential incoming
and outgoing changes and can deliver/accept if convenient.

Using RTC 3.0 iFix1, I opened a Word document from my sandbox using "Open With" to launch Word in a separate window.

After I saved my changes, I was surprised that the file did not appear in the "Pending Changes" view.

It works fine if I open the document in an Eclipse view, but I lose access to some of the Word functionality.

Is there a way to fix this behaviour, other than using Refresh?