$Web On: Difference between revisions
Jump to navigation
Jump to search
m (1 revision) |
m (1 revision) |
||
| Line 2: | Line 2: | ||
<span class="pageSubtitle"><section begin="desc" />Resume adding terminal output to response<section end="desc" /></span> | <span class="pageSubtitle"><section begin="desc" />Resume adding terminal output to response<section end="desc" /></span> | ||
$Web_On resumes the routing of terminal output to the client buffer. This buffer is sent to the client at the end of the connection. <var>$Web_Off</var> sends the output to the <var class="product">Model 204</var> audit trail. | <var>$Web_On</var> resumes the routing of terminal output to the client buffer. This buffer is sent to the client at the end of the connection. <var>$Web_Off</var> sends the output to the <var class="product">Model 204</var> audit trail. | ||
$Web_On takes no arguments and returns a status code. It is a callable $function (see [[Calling_Sirius_Mods_$functions|"Calling Sirius Mods $functions"]]). | <var>$Web_On</var> takes no arguments and returns a status code. It is a callable $function (see [[Calling_Sirius_Mods_$functions|"Calling Sirius Mods $functions"]]). | ||
==Syntax== | ==Syntax== | ||
Revision as of 22:43, 18 October 2012
<section begin="desc" />Resume adding terminal output to response<section end="desc" />
$Web_On resumes the routing of terminal output to the client buffer. This buffer is sent to the client at the end of the connection. $Web_Off sends the output to the Model 204 audit trail.
$Web_On takes no arguments and returns a status code. It is a callable $function (see "Calling Sirius Mods $functions").
Syntax
<section begin="syntax" />%rc = $Web_On <section end="syntax" />
Return codes
| Code | Meaning |
|---|---|
| 0 | Completed successfully. |
| -1 | Not a web thread |
Usage notes
- Output lines that are returned to the client browser by a $Web_On statement are not wrapped or truncated if their length exceeds the Model 204 LOBUFF parameter setting. Since some browsers do not render very long lines correctly (although no explicit guideline for "very long" is available), testing for your site's expected conditions and client browsers is advised if your output may contain such long lines with no CRLFs (line-wrapping breaks).