User Tools

Site Tools


transformations:exclusiveaccess

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
transformations:exclusiveaccess [2021/01/14 21:38] dmitrytransformations:exclusiveaccess [2021/01/16 07:43] – added image dmitry
Line 5: Line 5:
 The action is intended for avoiding access conflicts when two or more simultaneously executed projects (tasks) attempt to access a resource (e.g. write into a file or web API) that can only be accessed by one project at a time. It's typically used to resolve access conflicts between several simultaneously executed instances of an EasyMorph Server task. The action is intended for avoiding access conflicts when two or more simultaneously executed projects (tasks) attempt to access a resource (e.g. write into a file or web API) that can only be accessed by one project at a time. It's typically used to resolve access conflicts between several simultaneously executed instances of an EasyMorph Server task.
  
-The action works similarly to a railroad semaphore. When one project starts exclusive access to a resource using the action, all the other projects running on the same computer and requiring access to the same resource will wait until the first project finishes the exclusive access. Once exclusive access is finished, one from the waiting projects will proceed to access the same resource. +The action works similarly to a railroad semaphore. When one project starts exclusive access to a resource using the action, all the other projects running on the same computer and requiring access to the same resource will wait until the first project finishes the exclusive access. Once exclusive access is finished, one from the waiting projects will proceed to access the same resource. 
 + 
 +{{ :transformations:exclusive-access.png?nolink |}}
  
 For the access synchronization to work, all the projects that access the resource must use the "Start/finish exclusive access" with the same resource name. If a project doesn't use the action, it won't wait for another project even if the latter uses the action. For the access synchronization to work, all the projects that access the resource must use the "Start/finish exclusive access" with the same resource name. If a project doesn't use the action, it won't wait for another project even if the latter uses the action.
transformations/exclusiveaccess.txt · Last modified: 2021/10/14 11:18 by dmitry

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki