ContinueAsynchronously (Daemon subroutine) - Revision history

JAL2 at 22:56, 26 July 2012

2012-07-26T22:56:48Z

← Older revision		Revision as of 22:56, 26 July 2012
Line 1:		Line 1:
	{{Template:Daemon:ContinueAsynchronously subtitle}}		{{Template:Daemon:ContinueAsynchronously subtitle}}

	This method tells a daemon that issued a <var>Daemon</var> class <var>[[ReturnToMaster (Daemon subroutine)\|ReturnToMaster]]</var> call to continue processing at the point of ~~the~~ call. Unlike the <var>[[Continue (Daemon function)\|Continue]]</var> method, <var>ContinueAsynchronously</var> returns immediately, thus allowing the thread that issued <var>ContinueAsynchronously</var> to run in parallel with the daemon thread.		This method tells a daemon that issued a <var>Daemon</var> class <var>[[ReturnToMaster (Daemon subroutine)\|ReturnToMaster]]</var> call to continue processing from the point of that <var>ReturnToMaster</var> call. Unlike the <var>[[Continue (Daemon function)\|Continue]]</var> method, <var>ContinueAsynchronously</var> returns immediately, thus allowing the thread that issued <var>ContinueAsynchronously</var> to run in parallel with the daemon thread.

	==Syntax==		==Syntax==

JAL2: /* Exceptions */

2012-05-31T21:51:57Z

Exceptions

← Older revision		Revision as of 21:51, 31 May 2012
Line 21:		Line 21:
	<dd>If the daemon thread is not in a <var>ReturnToMaster</var> wait when <var>ContinueAsynchronously</var> is issued,		<dd>If the daemon thread is not in a <var>ReturnToMaster</var> wait when <var>ContinueAsynchronously</var> is issued,
	an <var>IncorrectDaemonState</var> exception is thrown. This exception will only be thrown in <var class="product">Sirius Mods</var> version 8.1 and later.		an <var>IncorrectDaemonState</var> exception is thrown. This exception will only be thrown in <var class="product">Sirius Mods</var> version 8.1 and later.

			<dt><var>[[DaemonLost_class\|DaemonLost]]</var>
			<dd>If <var class="term">daemon</var> is lost (probably restarted), a <var>DaemonLost</var> exception is thrown. Since <var>ContinueAsynchronously</var> does not wait for the <var>daemon</var> thread to do anything, a <var>DaemonLost</var> exception indicates that the daemon thread was lost <b><i>before</i></b> <var>ContinueAsynchronously</var> was invoked.
	</dl>		</dl>

JAL2: /* Usage notes */

2012-05-31T21:28:11Z

Usage notes

← Older revision		Revision as of 21:28, 31 May 2012
Line 28:		Line 28:

	<li>Issuing <var>ContinueAsynchronously</var> against a [[Daemon class#Transactional daemons\|transactional daemon]] results in request cancellation.		<li>Issuing <var>ContinueAsynchronously</var> against a [[Daemon class#Transactional daemons\|transactional daemon]] results in request cancellation.

			<li>If the <var class="term">daemon</var> thread and its daemons hold record locks that conflict with the parent thread's family (excluding the <var class="term">daemon</var> thread and its daemons), <var>ContinueAsynchronously</var> results in request cancellation.

	<li>Once started via <var>ContinueAsynchronously</var>, the <var class="term">daemon</var> thread is considered to be running asynchronously until a <var>[[WaitAsynchronous (Daemon function)\|WaitAsynchronous]]</var> is issued against the <var class="term">daemon</var> object. This is the case, even if the <var class="term">daemon</var> thread has completed processing all of the input commands.		<li>Once started via <var>ContinueAsynchronously</var>, the <var class="term">daemon</var> thread is considered to be running asynchronously until a <var>[[WaitAsynchronous (Daemon function)\|WaitAsynchronous]]</var> is issued against the <var class="term">daemon</var> object. This is the case, even if the <var class="term">daemon</var> thread has completed processing all of the input commands.

JAL2: /* Usage notes */

2012-05-31T21:26:48Z

Usage notes

← Older revision		Revision as of 21:26, 31 May 2012
Line 26:		Line 26:
	<ul>		<ul>
	<li>The <var>[[Continue (Daemon function)\|Continue]]</var> and <var>[[ContinueIndependently (Daemon subroutine)\|ContinueIndependently]]</var> methods also tell a daemon to continue from a <var>ReturnToMaster</var> wait.</li>		<li>The <var>[[Continue (Daemon function)\|Continue]]</var> and <var>[[ContinueIndependently (Daemon subroutine)\|ContinueIndependently]]</var> methods also tell a daemon to continue from a <var>ReturnToMaster</var> wait.</li>

			<li>Issuing <var>ContinueAsynchronously</var> against a [[Daemon class#Transactional daemons\|transactional daemon]] results in request cancellation.

	<li>Once started via <var>ContinueAsynchronously</var>, the <var class="term">daemon</var> thread is considered to be running asynchronously until a <var>[[WaitAsynchronous (Daemon function)\|WaitAsynchronous]]</var> is issued against the <var class="term">daemon</var> object. This is the case, even if the <var class="term">daemon</var> thread has completed processing all of the input commands.		<li>Once started via <var>ContinueAsynchronously</var>, the <var class="term">daemon</var> thread is considered to be running asynchronously until a <var>[[WaitAsynchronous (Daemon function)\|WaitAsynchronous]]</var> is issued against the <var class="term">daemon</var> object. This is the case, even if the <var class="term">daemon</var> thread has completed processing all of the input commands.

JAL2: /* Examples */

2012-05-31T21:18:48Z

Examples

← Older revision		Revision as of 21:18, 31 May 2012
Line 35:		Line 35:
	<li>For more information about asynchronous daemons, see [[Daemon class#Asynchronous and Independent daemons\|"Asynchronous and Independent daemons"]].		<li>For more information about asynchronous daemons, see [[Daemon class#Asynchronous and Independent daemons\|"Asynchronous and Independent daemons"]].
	</ul>		</ul>

	~~==Examples==~~

	==See also==		==See also==
	{{Template:Daemon:ContinueAsynchronously footer}}		{{Template:Daemon:ContinueAsynchronously footer}}

JAL2: /* Usage notes */

2012-05-31T21:17:23Z

Usage notes

← Older revision		Revision as of 21:17, 31 May 2012
Line 32:		Line 32:

	<li><var>WaitAsynchronous</var> is used to retrieve any output from the commands run via <var>ContinueAsynchronously</var>. This includes the terminal output and any output or info object.		<li><var>WaitAsynchronous</var> is used to retrieve any output from the commands run via <var>ContinueAsynchronously</var>. This includes the terminal output and any output or info object.

	<li>As described in: [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]], the <var>ContinueAsynchronously</var> <var class="term">commands</var> argument can pass multiple commands to the <var class="term">daemon</var> object.

	<li>For more information about asynchronous daemons, see [[Daemon class#Asynchronous and Independent daemons\|"Asynchronous and Independent daemons"]].		<li>For more information about asynchronous daemons, see [[Daemon class#Asynchronous and Independent daemons\|"Asynchronous and Independent daemons"]].

JAL2: /* Usage notes */

2012-05-31T21:14:55Z

Usage notes

@@ Line 26: / Line 26: @@
 <ul>
 <li>The <var>[[Continue (Daemon function)|Continue]]</var> and <var>[[ContinueIndependently (Daemon subroutine)|ContinueIndependently]]</var> methods also tell a daemon to continue from a <var>ReturnToMaster</var> wait.</li>
 </ul>

JAL2: /* Syntax terms */

2012-05-31T16:22:42Z

Syntax terms

← Older revision		Revision as of 16:22, 31 May 2012
Line 11:		Line 11:
	<td>A previously defined <var>Daemon</var> object. </td></tr>		<td>A previously defined <var>Daemon</var> object. </td></tr>
	<tr><th><var>Input</var></th>		<tr><th><var>Input</var></th>
	<td>This optional, [[Notation conventions for methods#Named parameters\|name allowed]], argument is an object passed to the <var class="term">daemon</var> thread. This object must be deep copyable, as described in: [[Copying objects\|"Copying objects"]].		<td>This optional, [[Notation conventions for methods#Named parameters\|name allowed]], argument is an object passed to the <var class="term">daemon</var> thread. This object must be deep copyable, as described in: [[Copying objects\|"Copying objects"]]. </td></tr>
	</table>		</table>

JAL2: /* Syntax terms */

2012-05-31T16:18:19Z

Syntax terms

← Older revision		Revision as of 16:18, 31 May 2012
Line 11:		Line 11:
	<td>A previously defined <var>Daemon</var> object. </td></tr>		<td>A previously defined <var>Daemon</var> object. </td></tr>
	<tr><th><var>Input</var></th>		<tr><th><var>Input</var></th>
	<td>This optional, [[Notation conventions for methods#Named parameters\|name allowed]], argument is ~~either:~~		<td>This optional, [[Notation conventions for methods#Named parameters\|name allowed]], argument is an object passed to the <var class="term">daemon</var> thread. This object must be deep copyable, as described in: [[Copying objects\|"Copying objects"]].
	~~<ul>~~
	~~<li>An~~ object passed to the <var class="term">daemon</var> thread. This object must be deep copyable, as described in: [[Copying objects\|"Copying objects"]].
	~~<li>A Boolean value. If a Null object~~
	~~</ul>~~
	</table>		</table>

JAL2: /* Syntax terms */

2012-05-31T16:15:43Z

Syntax terms

← Older revision		Revision as of 16:15, 31 May 2012
Line 10:		Line 10:
	<tr><th>daemon</th>		<tr><th>daemon</th>
	<td>A previously defined <var>Daemon</var> object. </td></tr>		<td>A previously defined <var>Daemon</var> object. </td></tr>
	<tr><th>~~object~~</th>		<tr><th><var>Input</var></th>
	<td>This optional, [[Notation conventions for methods#Named parameters\|name allowed]], argument is either:		<td>This optional, [[Notation conventions for methods#Named parameters\|name allowed]], argument is either:
	<ul>		<ul>