BINARY (JANUS DEFINE parameter): Difference between revisions
m (1 revision) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:BINARY}} | {{DISPLAYTITLE:BINARY}} | ||
<span class="pageSubtitle"><section begin="desc" /><section end="desc" /></span> | <span class="pageSubtitle"><section begin="desc" />Set BINARY mode for socket ports.<section end="desc" /></span> | ||
BINARY 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]]. | BINARY 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 requests ''[[Janus Sockets]]'' to send and receive strings with $SOCK_ functions or Socket methods using no translation. This can be useful if the ''[[Janus Sockets]]'' User Language application is doing its own translation, or if no translation is required. | This parameter requests ''[[Janus Sockets]]'' to send and receive strings with $SOCK_ functions or Socket methods using no translation. This can be useful if the ''[[Janus Sockets]]'' User Language application is doing its own translation, or if no translation is required. | ||
Input and output translation can be enabled for a socket by either of the following: | Input and output translation can be enabled for a socket by either of the following: | ||
<ul> | <ul> | ||
<li>Setting a socket to CHAR using [[$Sock_Set]] or the Set function of the Socket class | |||
<li>Setting a socket to CHAR using $ | |||
<li>Using the CHAR option on an individual receive or send $function or Socket method | <li>Using the CHAR option on an individual receive or send $function or Socket method | ||
</ul> | </ul> | ||
Character translation is automatic for the socket if you are using the HTTP Helper. | Character translation is automatic for the socket if you are using the HTTP Helper. | ||
| Line 20: | Line 19: | ||
Translation is determined by the tables defined by the socket's XTAB (:hdref reftxt=XTAB refid=xtab.) setting. | Translation is determined by the tables defined by the socket's XTAB (:hdref reftxt=XTAB refid=xtab.) setting. | ||
The CHAR parameter | The CHAR parameter is the opposite of BINARY. CHAR is the default. | ||
Valid only for CLSOCK and SRVSOCK ports. | Valid only for CLSOCK and SRVSOCK ports. | ||
Revision as of 19:26, 10 March 2011
<section begin="desc" />Set BINARY mode for socket ports.<section end="desc" />
BINARY is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port. See the List of JANUS DEFINE parameters.
This parameter requests Janus Sockets to send and receive strings with $SOCK_ functions or Socket methods using no translation. This can be useful if the Janus Sockets User Language application is doing its own translation, or if no translation is required.
Input and output translation can be enabled for a socket by either of the following:
- Setting a socket to CHAR using $Sock_Set or the Set function of the Socket class
- Using the CHAR option on an individual receive or send $function or Socket method
Character translation is automatic for the socket if you are using the HTTP Helper.
Individual strings can be translated using $SOCK_TRAN_IN or $SOCK_TRAN_OUT or their Socket method counterparts, TranIn or TranOut.
Translation is determined by the tables defined by the socket's XTAB (:hdref reftxt=XTAB refid=xtab.) setting.
The CHAR parameter is the opposite of BINARY. CHAR is the default.
Valid only for CLSOCK and SRVSOCK ports.
References
See: List of Janus commands | List of JANUS DEFINE parameters.