![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Longer to open Module in Read Mode vs. Share? Topic Summary: Opening a module using DXL in read seems to take longer than opening it in share when users have share locks on module. Created On: 20-Jul-2007 17:02 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Has anyone seen that opening a module in read mode (using DXL) seems to take significantly longer than opening a module in shared mode? One of my teammates swears that he is experiencing long open times (using read)...when the module has a couple user share locks on it. |
|
![]() |
|
![]() |
|
That would be odd since there's no particular reason the DOORS service would need to poll the clients that have the mdoule open Shared: no, the 'reader' should get whatever is on the server and doesn't care about any edits in progress.
The only thing that comes to mind is that the module may already be open 'shared' invisibly on that client due to its linking to some other module that's open. If so, opening shared means making it visible but opening it read means first closing it. Using "defopenlinkmode" of READ_ONLY in the registry may help that. You can see currently open modules via Tools >Manage Open Modules from the Explorer. - Louie |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.