EXEC2RPC (JANUS DEFINE parameter): Difference between revisions
m (moved EXEC2RPC to EXEC2RPC (JANUS DEFINE parameter)) |
mNo edit summary |
||
| Line 2: | Line 2: | ||
<span class="pageSubtitle"><section begin="desc" />Convert language requests to RPCs on OPENSERV ports<section end="desc" /></span> | <span class="pageSubtitle"><section begin="desc" />Convert language requests to RPCs on OPENSERV ports<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 [[JANUS DEFINE]], 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 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. | 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''. <var>EXEC2RPC</var> 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 <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 OPENSERV ports. | Valid only for OPENSERV ports. | ||
Revision as of 21:10, 24 February 2012
<section begin="desc" />Convert language requests to RPCs on OPENSERV ports<section end="desc" />
EXEC2RPC is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port. See the 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 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 OPENSERV ports.
References
See: List of Janus commands | List of JANUS DEFINE parameters.