RunIndependently (Daemon subroutine) - Revision history

JAL: /* Exceptions */ remove Sirius Mods version reference

2018-08-27T16:33:04Z

Exceptions: remove Sirius Mods version reference

← Older revision		Revision as of 16:33, 27 August 2018
Line 19:		Line 19:

	<dt><var>[[DaemonLost_class\|DaemonLost]]</var>		<dt><var>[[DaemonLost_class\|DaemonLost]]</var>
	<dd>If the <var>daemon</var> object is lost (probably restarted), a <var>DaemonLost</var> exception is thrown. Since <var>RunIndependently</var> does not wait for the <var>daemon</var> thread to do anything, a <var>DaemonLost</var> exception indicates that the <var>daemon</var> thread was lost <b><i>before</i></b> <var>RunIndependently</var> was invoked~~. This exception will only be thrown in <var class="product">[[Sirius Mods\|Sirius Mods]]</var> Version 7.2 and later~~.		<dd>If the <var>daemon</var> object is lost (probably restarted), a <var>DaemonLost</var> exception is thrown. Since <var>RunIndependently</var> does not wait for the <var>daemon</var> thread to do anything, a <var>DaemonLost</var> exception indicates that the <var>daemon</var> thread was lost <b><i>before</i></b> <var>RunIndependently</var> was invoked.
	</dl>		</dl>

JAL2: /* Exceptions */

2012-05-31T16:42:59Z

Exceptions

← Older revision		Revision as of 16:42, 31 May 2012
Line 16:		Line 16:

	==Exceptions==		==Exceptions==
	<var>RunIndependently</var> can throw the following ~~exceptions~~:<dl>		<var>RunIndependently</var> can throw the following exception:<dl>

	<dt><var>[[DaemonLost_class\|DaemonLost]]</var>		<dt><var>[[DaemonLost_class\|DaemonLost]]</var>

JAL2: /* Usage notes */

2012-05-22T20:57:41Z

Usage notes

← Older revision		Revision as of 20:57, 22 May 2012
Line 32:		Line 32:
	<li>No <var>Daemon</var> class mechanism is provided for a parent thread to retrieve the output from an independently running <var>Daemon</var>.		<li>No <var>Daemon</var> class mechanism is provided for a parent thread to retrieve the output from an independently running <var>Daemon</var>.
	<li>As described in [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]], the <var>RunIndependently</var> <var class="term">commands</var> argument can pass multiple commands to the <var class="term">daemon</var> method object.		<li>As described in [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]], the <var>RunIndependently</var> <var class="term">commands</var> argument can pass multiple commands to the <var class="term">daemon</var> method object.
			<li>For more information about independent daemons, see [[Daemon class#Asynchronous and Independent daemons\|"Asynchronous and Independent daemons"]].
	</ul>		</ul>

JAL2: /* Usage notes */

2012-05-22T19:05:42Z

Usage notes

← Older revision		Revision as of 19:05, 22 May 2012
Line 23:		Line 23:

	==Usage notes==		==Usage notes==
	<ul><li>Issuing <var>RunIndependently</var> against a [[Daemon class#Transactional daemons\|transactional daemon]] results in request cancellation.		<ul>
			<li>Issuing <var>RunIndependently</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 itself and its daemons), <var>RunIndependently</var> 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 itself and its daemons), <var>RunIndependently</var> results in request cancellation.
	<li><var>RunIndependently</var> is the rough <var>Daemon</var> class equivalent of the <var>[[$CommBg\|$~~commbg~~]]</var> function.		<li><var>RunIndependently</var> is the rough <var>Daemon</var> class equivalent of the <var>[[$CommBg\|$CommBg]]</var> function.
	<li>After a <var>RunIndependently</var> method, the <var class="term">daemon</var> object is set to null. This is because the <var class="term">daemon</var> thread runs completely independently of the parent thread once a <var>RunIndependently</var> method is invoked, so there is nothing useful the parent thread can do with such a daemon, anyway.		<li>After a <var>RunIndependently</var> method, the <var class="term">daemon</var> object is set to null. This is because the <var class="term">daemon</var> thread runs completely independently of the parent thread once a <var>RunIndependently</var> method is invoked, so there is nothing useful the parent thread can do with such a daemon, anyway.
	<li>The passing of objects and commands to daemons is identical whether the method is <var>[[Run_(Daemon_function)\|Run]]</var> or <var>RunIndependently</var> — see [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]] for more information about passing commands and objects to a daemon.		<li>The passing of objects and commands to daemons is identical whether the method is <var>[[Run_(Daemon_function)\|Run]]</var> or <var>RunIndependently</var> — see [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]] for more information about passing commands and objects to a daemon.

JAL2: /* Syntax terms */

2012-05-22T19:04:30Z

Syntax terms

← Older revision		Revision as of 19:04, 22 May 2012
Line 11:		Line 11:
	<tr><th>commands</th>		<tr><th>commands</th>
	<td>A string or <var>[[Stringlist class\|Stringlist]]</var> that is the command or the set of commands executed by the <var>daemon</var>.</td></tr>		<td>A string or <var>[[Stringlist class\|Stringlist]]</var> that is the command or the set of commands executed by the <var>daemon</var>.</td></tr>
	<tr><th>~~object~~</th>		<tr><th><var>Input</var></th>
	<td>An object passed to the <var class="term">daemon</var> object. This optional, [[Notation conventions for methods#Named parameters\|name allowed]], argument is passed by deep copy and not by reference, so <var class="term">object</var> must be deep copyable, as described in [[Copying objects\|"Copying objects"]].</td></tr>		<td>An object passed to the <var class="term">daemon</var> object. This optional, [[Notation conventions for methods#Named parameters\|name allowed]], argument is passed by deep copy and not by reference, so <var class="term">object</var> must be deep copyable, as described in [[Copying objects\|"Copying objects"]].</td></tr>
	</table>		</table>

JAL2 at 18:59, 22 May 2012

2012-05-22T18:59:23Z

← Older revision		Revision as of 18:59, 22 May 2012
Line 4:		Line 4:
	==Syntax==		==Syntax==
	{{Template:Daemon:RunIndependently syntax}}		{{Template:Daemon:RunIndependently syntax}}

	===Syntax terms===		===Syntax terms===
	<table class="syntaxTable">		<table class="syntaxTable">

JAL2: /* Usage notes */

2012-05-21T23:06:47Z

Usage notes

← Older revision		Revision as of 23:06, 21 May 2012
Line 22:		Line 22:

	==Usage notes==		==Usage notes==
	<ul><li>Issuing <var>RunIndependently</var> against a transactional ~~<var>~~daemon~~</var>~~ results in request cancellation.		<ul><li>Issuing <var>RunIndependently</var> against a [[Daemon class#Transactional daemons\|transactional daemon]] 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 itself and its ~~<var>~~daemons~~</var>~~ ), <var>RunIndependently</var> 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 itself and its daemons), <var>RunIndependently</var> results in request cancellation.
	<li><var>RunIndependently</var> is the rough ~~[[Daemon_class\|~~Daemon class]] equivalent of the <var>[[$CommBg\|$commbg]]</var> function.		<li><var>RunIndependently</var> is the rough <var>Daemon</var> class equivalent of the <var>[[$CommBg\|$commbg]]</var> function.
	<li>After a <var>RunIndependently</var> method, the <var>daemon</var> object is set to null. This is because the <var>daemon</var> thread runs completely independently of the parent thread once a <var>RunIndependently</var> method is invoked, so there is nothing useful the parent thread can do with such a ~~<var>~~daemon~~</var> object~~, anyway.		<li>After a <var>RunIndependently</var> method, the <var class="term">daemon</var> object is set to null. This is because the <var class="term">daemon</var> thread runs completely independently of the parent thread once a <var>RunIndependently</var> method is invoked, so there is nothing useful the parent thread can do with such a daemon, anyway.
	<li>The passing of objects and commands to daemons is identical whether the method is <var>[[Run_(Daemon_function)\|Run]]</var> or <var>RunIndependently</var> — see [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]] for more information about passing commands and objects to a daemon.		<li>The passing of objects and commands to daemons is identical whether the method is <var>[[Run_(Daemon_function)\|Run]]</var> or <var>RunIndependently</var> — see [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]] for more information about passing commands and objects to a daemon.
	<li>Even if the parent thread of an independently running ~~<var>~~daemon~~</var>~~ logs off, the ~~<var>~~daemon~~</var>~~ thread can continue to run.		<li>Even if the parent thread of an independently running daemon logs off, the daemon thread can continue to run.
	<li>No <var>~~daemon~~</var> class mechanism is provided for a parent thread to retrieve the output from an independently running <var>~~daemon~~</var>.		<li>No <var>Daemon</var> class mechanism is provided for a parent thread to retrieve the output from an independently running <var>Daemon</var>.
	<li>As described in [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]], <var>RunIndependently's</var> <var class="term">commands</var> argument can pass multiple commands to the <var>daemon</var>.		<li>As described in [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]], the <var>RunIndependently</var> <var class="term">commands</var> argument can pass multiple commands to the <var class="term">daemon</var> method object.
	</ul>		</ul>

JAL2 at 22:49, 21 May 2012

2012-05-21T22:49:50Z

← Older revision		Revision as of 22:49, 21 May 2012
Line 10:		Line 10:
	<tr><th>commands</th>		<tr><th>commands</th>
	<td>A string or <var>[[Stringlist class\|Stringlist]]</var> that is the command or the set of commands executed by the <var>daemon</var>.</td></tr>		<td>A string or <var>[[Stringlist class\|Stringlist]]</var> that is the command or the set of commands executed by the <var>daemon</var>.</td></tr>
	<tr><th>~~inputObj~~</th>		<tr><th>object</th>
	<td>~~The~~ object passed to the <var>daemon</var> object. This optional argument is passed by deep copy and not by reference, so <var class="term">~~inputObj~~</var> must be deep copyable, as described in [[Copying objects\|"Copying objects"]].</td></tr>		<td>An object passed to the <var class="term">daemon</var> object. This optional, [[Notation conventions for methods#Named parameters\|name allowed]], argument is passed by deep copy and not by reference, so <var class="term">object</var> must be deep copyable, as described in [[Copying objects\|"Copying objects"]].</td></tr>
	</table>		</table>

Line 26:		Line 26:
	<li><var>RunIndependently</var> is the rough [[Daemon_class\|Daemon class]] equivalent of the <var>[[$CommBg\|$commbg]]</var> function.		<li><var>RunIndependently</var> is the rough [[Daemon_class\|Daemon class]] equivalent of the <var>[[$CommBg\|$commbg]]</var> function.
	<li>After a <var>RunIndependently</var> method, the <var>daemon</var> object is set to null. This is because the <var>daemon</var> thread runs completely independently of the parent thread once a <var>RunIndependently</var> method is invoked, so there is nothing useful the parent thread can do with such a <var>daemon</var> object, anyway.		<li>After a <var>RunIndependently</var> method, the <var>daemon</var> object is set to null. This is because the <var>daemon</var> thread runs completely independently of the parent thread once a <var>RunIndependently</var> method is invoked, so there is nothing useful the parent thread can do with such a <var>daemon</var> object, anyway.
			<li>The passing of objects and commands to daemons is identical whether the method is <var>[[Run_(Daemon_function)\|Run]]</var> or <var>RunIndependently</var> — see [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]] for more information about passing commands and objects to a daemon.
	<li>Even if the parent thread of an independently running <var>daemon</var> logs off, the <var>daemon</var> thread can continue to run.		<li>Even if the parent thread of an independently running <var>daemon</var> logs off, the <var>daemon</var> thread can continue to run.
	<li>No <var>daemon</var> class mechanism is provided for a parent thread to retrieve the output from an independently running <var>daemon</var>.		<li>No <var>daemon</var> class mechanism is provided for a parent thread to retrieve the output from an independently running <var>daemon</var>.
	<li>As described in [[Daemon class]], <var>RunIndependently's</var> <var class="term">~~string~~</var> argument can pass multiple commands to the <var>daemon</var>.		<li>As described in [[Daemon class#Working with Daemon objects\|"Working with Daemon objects"]], <var>RunIndependently's</var> <var class="term">commands</var> argument can pass multiple commands to the <var>daemon</var>.
	~~<li><var>RunIndependently</var> was introduced in <var class="product">[[Sirius Mods\|Sirius Mods]]</var> Version 7.0~~.
	</ul>		</ul>

	==Examples==		==Examples==
	~~<ol><li>~~<p class="code">%daem:runIndependently(%list2, %x)		<p class="code">%daem:runIndependently(%list2, %x)
	</p>		</p>
	~~</ol>~~

	==See also==		==See also==
	<ul><li>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 <var>[[Run_(Daemon_function)\|Run]]</var> or <var>RunIndependently</var>.</ul>
	{{Template:Daemon:RunIndependently footer}}		{{Template:Daemon:RunIndependently footer}}

Dme: /* Syntax terms */

2011-05-22T21:19:52Z

Syntax terms

← Older revision		Revision as of 21:19, 22 May 2011
Line 9:		Line 9:
	<td>A previously defined <var>Daemon</var> object. </td></tr>		<td>A previously defined <var>Daemon</var> object. </td></tr>
	<tr><th>commands</th>		<tr><th>commands</th>
	<td>A string or <var>[[Stringlist class\|Stringlist]]</var> that is the ~~required~~ command or the set of commands executed by the <var>daemon</var>.</td></tr>		<td>A string or <var>[[Stringlist class\|Stringlist]]</var> that is the command or the set of commands executed by the <var>daemon</var>.</td></tr>
	<tr><th>inputObj</th>		<tr><th>inputObj</th>
	<td>The object passed to the <var>daemon</var> object. This optional argument is passed by deep copy and not by reference, so <var class="term">inputObj</var> must be deep copyable, as described in [[Copying objects\|"Copying objects"]].</td></tr>		<td>The object passed to the <var>daemon</var> object. This optional argument is passed by deep copy and not by reference, so <var class="term">inputObj</var> must be deep copyable, as described in [[Copying objects\|"Copying objects"]].</td></tr>

JALWiccan: 1 revision

2011-05-04T17:46:15Z

1 revision

← Older revision	Revision as of 17:46, 4 May 2011
(No difference)