BINARY (JANUS DEFINE parameter): Difference between revisions
Jump to navigation
Jump to search
m (1 revision) |
(Automatically generated page update) |
||
| (21 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
<span class="pageSubtitle">Set BINARY mode for socket ports</span> | |||
<span class="pageSubtitle"> | |||
BINARY is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port | <var>BINARY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
This parameter requests <var class="product">[[Janus Sockets]]</var> to send and receive strings with [[Janus Sockets $functions]] or <var>[[Socket class|Socket]]</var> [[List of Socket methods|methods]] using no translation. This can be useful if the <var class="product">Janus Sockets</var> <var class="product">User Language</var> 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: | |||
<ul> | <ul> | ||
<li>Setting a socket to <var>CHAR</var> using <var>[[$Sock_Set]]</var> or the <var>[[Set (Socket function)|Set]]</var> function of the <var>Socket</var> class | |||
<li>Using the <var>CHAR</var> option on an individual receive or send <var class="product">Janus Sockets</var> $function or <var>Socket</var> class method | |||
</ul> | |||
Character translation is automatic for the socket if you are using the <var>[[HTTP Helper]]</var>. | |||
Character translation is automatic for the socket if you are using the HTTP Helper. | |||
Individual strings can be translated using $ | Individual strings can be translated using <var>[[$Sock_Tran_In]]</var> or <var>[[$Sock_Tran_Out]]</var> or their <var>Socket</var> method counterparts, <var>[[TranIn (Socket function)|TranIn]]</var> or <var>[[TranOut (Socket function)|TranOut]]</var>. | ||
Translation is determined by the tables defined by the socket's XTAB ( | Translation is determined by the tables defined by the socket's <var>[[XTAB (JANUS DEFINE parameter)|XTAB]]</var> setting. | ||
The CHAR parameter | The <var>[[CHAR (JANUS DEFINE parameter)|CHAR]]</var> parameter is the opposite of <var>BINARY</var>. <var>CHAR</var> is the default. | ||
Valid only for CLSOCK and SRVSOCK ports. | Valid only for <var>[[JANUS DEFINE#type|CLSOCK]]</var> and <var>[[JANUS DEFINE#type|SRVSOCK]]</var> ports. | ||
== | ==See also== | ||
<ul> | |||
<li>[[List of Janus commands]] | |||
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] | |||
</ul> | |||
[[Category:JANUS DEFINE parameters|BINARY]] | [[Category:JANUS DEFINE parameters|BINARY]] | ||
Latest revision as of 21:50, 16 April 2013
Set BINARY mode for socket ports
BINARY is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
This parameter requests Janus Sockets to send and receive strings with Janus Sockets $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 Janus Sockets $function or Socket class 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 setting.
The CHAR parameter is the opposite of BINARY. CHAR is the default.
Valid only for CLSOCK and SRVSOCK ports.