EXEC2RPC (JANUS DEFINE parameter) - Revision history

JAL: remove displaytitle

2016-06-08T18:06:46Z

remove displaytitle

← Older revision		Revision as of 18:06, 8 June 2016
Line 1:		Line 1:
	~~{{DISPLAYTITLE:EXEC2RPC}}~~
	<span class="pageSubtitle">Convert language requests to RPCs on OPENSERV ports</span>		<span class="pageSubtitle">Convert language requests to RPCs on OPENSERV ports</span>

	<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the <var class="~~product~~">[~~http~~:~~//sirius-software.com/maint/download/josrv~~.pdf Janus Open Server Reference Manual]</var>. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port ~~so that~~ Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to ~~the~~ <var class="product">~~User Language~~</var> via $~~SRV_LANGGET~~. If a language request is converted to an RPC, $~~SRV_WAIT~~ returns a 1 indicating that an RPC has been received. Thus, it is impossible for a <var class="product">~~User Language~~</var> application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.		This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the <var class="book">[[Media:JosrvNew.pdf\|Janus Open Server Reference Manual]]</var>.

			<var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port to satisfy the following scenario: Janus attempts to convert language requests into RPCs, but if the attempt fails, the language request is then made available to <var class="product">SOUL</var> via <var>$Srv_Langget</var>. If a language request is converted to an RPC, <var>$Srv_Wait<var> returns a 1 indicating that an RPC has been received. Thus, it is impossible for a <var class="product">SOUL</var> application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.

	Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.		Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.

JAL at 22:14, 16 April 2013

2013-04-16T22:14:16Z

← Older revision		Revision as of 22:14, 16 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:EXEC2RPC}}		{{DISPLAYTITLE:EXEC2RPC}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>Convert language requests to RPCs on OPENSERV ports~~<section end="desc" />~~</span>		<span class="pageSubtitle">Convert language requests to RPCs on OPENSERV ports</span>

	<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JAL2 at 21:31, 1 March 2012

2012-03-01T21:31:30Z

← Older revision		Revision as of 21:31, 1 March 2012
Line 1:		Line 1:
	{{DISPLAYTITLE:EXEC2RPC}}		{{DISPLAYTITLE:EXEC2RPC}}
	<span class="pageSubtitle"><section begin="desc" />Convert language requests to RPCs on ~~<var>[[JANUS DEFINE#type\|~~OPENSERV~~]]</var>~~ ports<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Convert language requests to RPCs on OPENSERV ports<section end="desc" /></span>

	<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JALWiccan: 1 revision

2012-03-01T21:27:35Z

1 revision

← Older revision	Revision as of 21:27, 1 March 2012
(No difference)

JALWiccan: 1 revision

2012-03-01T21:27:33Z

1 revision

← Older revision		Revision as of 21:27, 1 March 2012
Line 4:		Line 4:
	<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the <var class="product">[http://sirius-software.com/maint/download/josrv.pdf Janus Open Server Reference Manual]</var>. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.		This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the <var class="product">[http://sirius-software.com/maint/download/josrv.pdf Janus Open Server Reference Manual]</var>. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a <var class="product">User Language</var> application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.

	Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.		Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.

JALWiccan: 1 revision

2012-02-29T22:33:22Z

1 revision

← Older revision	Revision as of 22:33, 29 February 2012
(No difference)

JAL2 at 22:33, 29 February 2012

2012-02-29T22:33:19Z

← Older revision		Revision as of 22:33, 29 February 2012
Line 2:		Line 2:
	<span class="pageSubtitle"><section begin="desc" />Convert language requests to RPCs on <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Convert language requests to RPCs on <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports<section end="desc" /></span>

	<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port~~. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]~~.		<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the <var class="product">[http://sirius-software.com/maint/download/josrv.pdf Janus Open Server Reference Manual]</var>. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.		This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the <var class="product">[http://sirius-software.com/maint/download/josrv.pdf Janus Open Server Reference Manual]</var>. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.

JAL2 at 18:26, 29 February 2012

2012-02-29T18:26:27Z

← Older revision		Revision as of 18:26, 29 February 2012
Line 4:		Line 4:
	<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].		<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].

	This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the ''Janus Open Server Reference Manual''. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.		This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the <var class="product">[http://sirius-software.com/maint/download/josrv.pdf Janus Open Server Reference Manual]</var>. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.

	Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.		Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.

JAL2 at 18:25, 29 February 2012

2012-02-29T18:25:15Z

← Older revision		Revision as of 18:25, 29 February 2012
Line 2:		Line 2:
	<span class="pageSubtitle"><section begin="desc" />Convert language requests to RPCs on <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Convert language requests to RPCs on <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports<section end="desc" /></span>

	<var>EXEC2RPC</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].		<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].

	This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the ''Janus Open Server Reference Manual''. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.		This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the ''Janus Open Server Reference Manual''. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.
Line 8:		Line 8:
	Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.		Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.

	==~~References~~==		==See also==
			<ul>
	~~See:~~ [[List of Janus commands]] \| [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].		<li>[[List of Janus commands]]
			<li>[[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]
			</ul>

	[[Category:JANUS DEFINE parameters\|EXEC2RPC]]		[[Category:JANUS DEFINE parameters\|EXEC2RPC]]

JALWiccan: 1 revision

2012-02-29T18:18:57Z

1 revision

← Older revision	Revision as of 18:18, 29 February 2012
(No difference)

← Older revision		Revision as of 18:26, 29 February 2012
Line 4:		Line 4:
	<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].		<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].

	This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the ''Janus Open Server Reference Manual''. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.		This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the <var class="product">[http://sirius-software.com/maint/download/josrv.pdf Janus Open Server Reference Manual]</var>. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.

	Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.		Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.

← Older revision		Revision as of 18:25, 29 February 2012
Line 2:		Line 2:
	<span class="pageSubtitle"><section begin="desc" />Convert language requests to RPCs on <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Convert language requests to RPCs on <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports<section end="desc" /></span>

	<var>EXEC2RPC</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].		<var>EXEC2RPC</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].

	This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the ''Janus Open Server Reference Manual''. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.		This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC are described in the ''Janus Open Server Reference Manual''. <var>EXEC2RPC</var> implies <var>[[RPCONLY (JANUS DEFINE parameter)\|RPCONLY]]</var>. That is, it is not possible to set up a port so that Janus attempts to convert language requests into RPCs but if the attempt fails the language request is then made available to the <var class="product">User Language</var> via $SRV_LANGGET. If a language request is converted to an RPC, $SRV_WAIT returns a 1 indicating that an RPC has been received. Thus, it is impossible for a User Language application on an <var>EXEC2RPC</var> port to tell if the current request was a "true" RPC or one that was generated via <var>EXEC2RPC</var>.
Line 8:		Line 8:
	Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.		Valid only for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports.

	==~~References~~==		==See also==
			<ul>
	~~See:~~ [[List of Janus commands]] \| [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].		<li>[[List of Janus commands]]
			<li>[[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]
			</ul>

	[[Category:JANUS DEFINE parameters\|EXEC2RPC]]		[[Category:JANUS DEFINE parameters\|EXEC2RPC]]