EXEC2RPC (JANUS DEFINE parameter): Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (1 revision)
m (remove displaytitle)
 
(14 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:EXEC2RPC}}
<span class="pageSubtitle">Convert language requests to RPCs on OPENSERV ports</span>
<span class="pageSubtitle"><section begin="desc" /><section end="desc" /></span>


EXEC2RPC 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.  


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>.


This parameter indicates that language requests should be converted to RPCs. The types of language requests that can be translated into an RPC is described in the ''Janus Open Server Reference Manual''. EXEC2RPC implies RPCONLY. 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 User Language 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 EXEC2RPC port to tell if the current request was a "true" RPC or one that was generated via EXEC2RPC.  
Valid only for <var>[[JANUS DEFINE#type|OPENSERV]]</var> ports.


Valid only for OPENSERV ports.
==See also==
 
<ul>
==References==
<li>[[List of Janus commands]]
 
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]]
See: [[List of Janus commands]] | [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]].
</ul>


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

Latest revision as of 18:06, 8 June 2016

Convert language requests to RPCs on OPENSERV ports

EXEC2RPC is a parameter on JANUS DEFINE, 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 Janus Open Server Reference Manual.

EXEC2RPC implies RPCONLY. 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 SOUL 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 SOUL application on an EXEC2RPC port to tell if the current request was a "true" RPC or one that was generated via EXEC2RPC.

Valid only for OPENSERV ports.

See also

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=EXEC2RPC_(JANUS_DEFINE_parameter)&oldid=84541"