ClearSCADA

compared with
Current by Adam Woodland
on May 16, 2017 23:39.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History
|Execution|Server-side|Client-side|
|Reliability|Always runs (whilst the logic driver is running)|Requires user to be logged in and to display a suitable mimic. Susceptible to network failure between client and server|
|Security|Requires configuration permission to create and edit, runs within the context of the server|Requires configuration permission to create and edit, runs within the context of the logged in user|
|Permissions|Requires configuration permission to create and edit|Requires configuration permission to create and edit|
|Security Context|Runs within the context of the ClearSCADA server|Runs within the context of the current user, both ClearSCADA and Windows environments
|Threading|Single thread running on the server, execution cannot be aborted however refer to [Logic Execution] for parallel handling of inputs and outputs|Single thread running on each client, execution can be aborted by other scripting or by the user|
|Execution Performance|Extremely quick, although care should be taken with SQL queries as they may significantly impact server availability due to the query itself or the frequency of the query execution|Slower than logic, subject to bandwidth issues and latency on the network due to the server calls, and to both overall client and server performance|
|User Interface|No interface, dialogue when manually executed asking for any input parameters|Basic form functionality and the ability to interact with mimics|
|Ease of Learning|If you are used to PLC coding it is a similar concept; different to typical IT type coding|Uses Microsoft ActiveScript so a large choice of languages including VBScript and JavaScript. Plenty of resources online for reference|
|Data Type|Strongly typed|Weakly typed (language dependent)|
|Error Checking|Syntax and object reference at compile time, no exception handling in code|Syntax checks are compile time, object references during runtime, exception handling in code (i.e. On Error in VBScript)|
|File Handling|Limited ability to write to files (and COM ports)|Extensive functions using any installed COM libraries, for example FileSystemObject|

h2. See Also