RunAsynchronously (Daemon subroutine): Difference between revisions
Jump to navigation
Jump to search
m (→Exceptions) |
m (→Usage notes) |
||
| Line 26: | Line 26: | ||
<li>Issuing <var>RunAsynchronously</var> against a transactional <var>daemon</var> results in request cancellation. | <li>Issuing <var>RunAsynchronously</var> against a transactional <var>daemon</var> results in request cancellation. | ||
<li>If the <var>daemon</var> thread and its <var>daemons</var> hold record locks that conflict with the parent thread's family (excluding the <var>daemon</var> thread and its <var>daemons</var>), <var>RunAsynchronously</var> results in request cancellation. | <li>If the <var>daemon</var> thread and its <var>daemons</var> hold record locks that conflict with the parent thread's family (excluding the <var>daemon</var> thread and its <var>daemons</var>), <var>RunAsynchronously</var> results in request cancellation. | ||
<li>Once started via <var>RunAsynchronously</var>, the <var>daemon</var> thread is considered to be running asynchronously until a <var>[[WaitAsynchronous (Daemon function)|WaitAsynchronous]]</var> is issued against the <var>daemon</var> object. This is the case, even if the <var>daemon</var> thread has completed processing all of the input commands. | <li>Once started via <var>RunAsynchronously</var>, the <var>daemon</var> thread is considered to be running asynchronously until a <var>[[WaitAsynchronous (Daemon function)|WaitAsynchronous]]</var> is issued against the <var>daemon</var> object. This is the case, even if the <var>daemon</var> thread has completed processing all of the input commands. | ||
<li>While the <var>daemon</var> thread is running asynchronously, any methods that require interaction with the <var>daemon</var> thread cause request cancellation. These methods include <var>[[Run_(Daemon_function)|Run]]</var>, <var>RunAsynchronously</var>, <var>[[RunIndependently_(Daemon_subroutine)|RunIndependently]]</var>, <var>[[Open_(Daemon_subroutine)|Open]]</var>, and <var>[[LastCommandErrorCount_(Daemon_property)|LastCommandErrorCount]]</var>. | <li>While the <var>daemon</var> thread is running asynchronously, any methods that require interaction with the <var>daemon</var> thread cause request cancellation. These methods include <var>[[Run_(Daemon_function)|Run]]</var>, <var>RunAsynchronously</var>, <var>[[RunIndependently_(Daemon_subroutine)|RunIndependently]]</var>, <var>[[Open_(Daemon_subroutine)|Open]]</var>, and <var>[[LastCommandErrorCount_(Daemon_property)|LastCommandErrorCount]]</var>. | ||
<li><var> | |||
<li>As described in: [[Daemon class#Working with Daemonobjects|"Working with Daemon objects"]], <var>RunAsynchronously | <li><var>WaitAsynchronous</var> is used to retrieve any output from the commands run via <var>RunAsynchronously</var>. This includes the terminal output and any output or info object. | ||
<li>See [[Daemon class|"Daemon class"]] for more information about passing commands and objects to a daemon | |||
<li>As described in: [[Daemon class#Working with Daemonobjects|"Working with Daemon objects"]], <var>RunAsynchronously</var>'s <var>String</var> argument can pass multiple commands to the <var>daemon</var>. | |||
<li>See [[Daemon class|"Daemon class"]] for more information about passing commands and objects to a daemon — the passing of objects and commands to daemons is identical whether the method is <var>Run</var> or <var>RunAsynchronously</var>. | |||
<li>If the <var>daemon</var> object associated with an asynchronously running <var>daemon</var> is discarded, either explicitly or implicitly; the <var>daemon</var> thread is bumped by the parent thread. An implicit discard can happen at request end (for non-global daemon objects) or at user logout. | <li>If the <var>daemon</var> object associated with an asynchronously running <var>daemon</var> is discarded, either explicitly or implicitly; the <var>daemon</var> thread is bumped by the parent thread. An implicit discard can happen at request end (for non-global daemon objects) or at user logout. | ||
<li>The inputs and outputs from the combination of <var>RunAsynchronously</var> and <var> | |||
<li>The inputs and outputs from the combination of <var>RunAsynchronously</var> and <var>WaitAsynchronous</var> are identical to the inputs and outputs from <var>Run</var>. As such, it should be a relatively simple task to split a <var>Run</var> into a <var>RunAsynchronously</var> and <var>WaitAsynchronous</var>, allowing the daemon processing to be performed in parallel with parent thread processing or the processing on another daemon thread. | |||
<p>For example, if a request has the following statements:</p> | <p>For example, if a request has the following statements:</p> | ||
<p class="code">%out1 = %daem1:run(%cmds1, %inobj1, %outobj1) | |||
%out2 = %daem2:run(%cmds2, %inobj2, %outobj2) | %out2 = %daem2:run(%cmds2, %inobj2, %outobj2) | ||
</p> | </p> | ||
| Line 43: | Line 50: | ||
%out2 = %daem2:waitAsynchronous(%outobj2) | %out2 = %daem2:waitAsynchronous(%outobj2) | ||
</p> | </p> | ||
<p>Note that this will buy nothing if the requests are CPU-intensive and the request is not running with AMPSUBS>0 (requires < | <p>Note that this will buy nothing if the requests are CPU-intensive and the request is not running with <code>AMPSUBS>0</code> (requires <var class="product">MP/204</var>). Note also that if the daemons hold or require record locks that might conflict with each other, such a split will not work. Finally, since <var>RunAsynchronously</var> is not allowed for a transactional daemon, such a split is not feasible for transactional daemons.</p> | ||
</ul> | </ul> | ||
==Examples== | ==Examples== | ||
<p class="code">%daem:runAsynchronously(%list2, %x) | <p class="code">%daem:runAsynchronously(%list2, %x) | ||
Revision as of 23:34, 17 May 2012
Run commands on the Daemon thread asynchronously (Daemon class)
RunAsynchronously runs on the daemon thread the command or set of commands specified by its first argument. Unlike the Run method, RunAsynchronously returns immediately allowing the thread issuing RunAsynchronously to run in parallel with the daemon thread.
Syntax
daemon:RunAsynchronously( commands, [[Input=] object]) Throws DaemonLost, IncorrectDaemonState
Syntax terms
| daemon | A previously defined Daemon object. |
|---|---|
| commands | A string or Stringlist that is the command or the set of commands executed by the daemon. |
| inputObj | The object passed to daemon object. This optional argument is passed by deep copy and not by reference, so inputObj must be deep copyable, as described in: "Copying objects". The passed object can be retrieved by the daemon thread using the GetInputObject. |
Exceptions
RunAsynchronously can throw the following exception:
- DaemonLost
- If daemon is lost (probably restarted), a DaemonLost exception is thrown. Since RunAsynchronously does not wait for the daemon thread to do anything, a DaemonLost exception indicates that the daemon thread was lost before RunAsynchronously was invoked. This exception will only be thrown in Sirius Mods Version 7.2 and later.
Usage notes
- Issuing RunAsynchronously against a transactional daemon results in request cancellation.
- If the daemon thread and its daemons hold record locks that conflict with the parent thread's family (excluding the daemon thread and its daemons), RunAsynchronously results in request cancellation.
- Once started via RunAsynchronously, the daemon thread is considered to be running asynchronously until a WaitAsynchronous is issued against the daemon object. This is the case, even if the daemon thread has completed processing all of the input commands.
- While the daemon thread is running asynchronously, any methods that require interaction with the daemon thread cause request cancellation. These methods include Run, RunAsynchronously, RunIndependently, Open, and LastCommandErrorCount.
- WaitAsynchronous is used to retrieve any output from the commands run via RunAsynchronously. This includes the terminal output and any output or info object.
- As described in: "Working with Daemon objects", RunAsynchronously's String argument can pass multiple commands to the daemon.
- See "Daemon class" for more information about passing commands and objects to a daemon — the passing of objects and commands to daemons is identical whether the method is Run or RunAsynchronously.
- If the daemon object associated with an asynchronously running daemon is discarded, either explicitly or implicitly; the daemon thread is bumped by the parent thread. An implicit discard can happen at request end (for non-global daemon objects) or at user logout.
- The inputs and outputs from the combination of RunAsynchronously and WaitAsynchronous are identical to the inputs and outputs from Run. As such, it should be a relatively simple task to split a Run into a RunAsynchronously and WaitAsynchronous, allowing the daemon processing to be performed in parallel with parent thread processing or the processing on another daemon thread.
For example, if a request has the following statements:
%out1 = %daem1:run(%cmds1, %inobj1, %outobj1) %out2 = %daem2:run(%cmds2, %inobj2, %outobj2)
The statements can be easily split up into the following ones, and the processing on the two daemons would be performed in parallel with each other:
%daem1:runAsynchronously(%cmds1, %inobj1) %daem2:runAsynchronously(%cmds2, %inobj2) %out1 = %daem1:waitAsynchronous(%outobj1) %out2 = %daem2:waitAsynchronous(%outobj2)
Note that this will buy nothing if the requests are CPU-intensive and the request is not running with
AMPSUBS>0(requires MP/204). Note also that if the daemons hold or require record locks that might conflict with each other, such a split will not work. Finally, since RunAsynchronously is not allowed for a transactional daemon, such a split is not feasible for transactional daemons.
Examples
%daem:runAsynchronously(%list2, %x)