That's easy.
RTC would be pulling *all* the files accross the slow network.
The rsync mechanism would be pushing the files accross the connection when engineers were still sleeping. They would be downloading a majority of the files on their local (fast) network, and only updating changes from accross the very slow network. We so this today and it is significant. |
One answer
Ah, I see, Here are some of my thoughts. Your current solution makes use
of RSync and Subversion, I am guessing that you have RSync scheduled each night and then you use Subversion to check files in. Jazz (like subversion) has a command line client. Now the "load" command will Load/Update a repository workspace onto the local filesystem. You can use this to mimic your rsync and add this as a cronjob/system scheduled task. Your users can then continue to use that same tool to check-in, resolve conflicts, and use the rest of the Jazz SCM Client functionality. ScottChapman wrote: RTC would be pulling *all* the files accross the slow network. |
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.