$Web On: Difference between revisions
m (1 revision) |
m (1 revision) |
||
Line 26: | Line 26: | ||
<ul> | <ul> | ||
<li>[[$Web_Off]] | <li>[[<var>$Web_Off]]</var> | ||
<li>[[$Web_Flush]] | <li>[[<var>$Web_Flush]]</var> | ||
<li>[[$Web_Put_Text]] | <li>[[<var>$Web_Put_Text]]</var> | ||
</ul> | </ul> | ||
[[Category:Janus Web Server $functions|$Web_On]] | [[Category:Janus Web Server $functions|$Web_On]] |
Revision as of 20:17, 12 June 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.
Syntax
<section begin="syntax" /> %RC = $Web_On <section end="syntax" />
$Web_On takes no arguments and returns a status code. It is a callable $function (see Calling Sirius Mods $functions).
Code | Meaning |
---|---|
0 | Completed successfully. |
-1 | Not a web thread |
As of Version 6.4 of the Sirius Mods, 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).
For more information about $Web_On and $Web_Off processing, see:
- [[$Web_Off]]
- [[$Web_Flush]]
- [[$Web_Put_Text]]