RTC resource control

RTC 2.0 will provide file level locking, meaning that you can prevent other users from delivering changes to a file you have locked in a specific stream.

In your example, user A would have to lock the file before starting work, which would prevent B from delivering changes to it (as well as informing B that they should expect a change in the near future).

e

Note though that this will not prevent the other user from working on
the file ... it will only prevent them from delivering the parallel
changes to the stream (but that is really too late ... by then the
conflict exists).

The fact that the file is locked is shown in the GUI, so although the
user cannot currently be prevented from making changes to the file,
there is at least a GUI indication that this is likely to create a
conflict at deliver time.

There is a work item to actually prevent the parallel work from
happening (work item 77416) and to warn them (work item 77225).

Cheers,
Geoff

echughes wrote:

RTC 2.0 will provide file level locking, meaning that you can prevent
other users from delivering changes to a file you have locked in a
specific stream.

In your example, user A would have to lock the file before starting
work, which would prevent B from delivering changes to it (as well as
informing B that they should expect a change in the near future).

e