Customization Considerations with Multi-threading
Any developer creating tools for Contenta Web must consider the need for transaction synchronization if tools use multiple panes or have multiple threads. By default, multiple panes imply multiple threads.
In addition, if any of the delivered Contenta Web programs are customized, the developer must take care to ensure that transaction synchronization is used when necessary.
However, to minimize the impact on performance, transaction synchronization must only be applied to the smallest subset of Portal commands where those commands rely on the execution of earlier commands—for example, the selection of an object and listing of its children must be wrapped with transaction on and off commands.