MSGSEND and NOMSGSEND (JANUS DEFINE parameters): Difference between revisions
mNo edit summary |
(Automatically generated page update) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:MSGSEND and NOMSGSEND}} | {{DISPLAYTITLE:MSGSEND and NOMSGSEND}} | ||
<span class="pageSubtitle" | <span class="pageSubtitle">Enable/Disable sending of 204 messages to web browser.</span> | ||
<var>MSGSEND</var> and <var>NOMSGSEND</var> are parameters on <var>[[JANUS DEFINE]]</var>, whichs define and sets characteristics of a Janus port | <var>MSGSEND</var> and <var>NOMSGSEND</var> are parameters on <var>[[JANUS DEFINE]]</var>, whichs define and sets characteristics of a Janus port. | ||
Indicates whether or not | Indicates whether or not <var class="product">Model 204</var> messages (as opposed to the output from PRINT or HTML statements) are to be sent to the browser. | ||
For backward compatibility, the default for this parameter is <var>MSGSEND</var>, though <var>NOMSGSEND</var> is probably more useful for most applications. | For backward compatibility, the default for this parameter is <var>MSGSEND</var>, though <var>NOMSGSEND</var> is probably more useful for most applications. | ||
<var class="product">Model 204</var> messages include informatory messages such as those issued when a file is opened or closed, error messages, and messages and warnings from other users sent by MSG or WARN commands. <var>MSGSEND</var> or <var>NOMSGSEND</var> can be overridden by a <var>MSGSEND</var> or <var>NOMSGSEND</var> parameter in a JANUS WEB ON rule or in a $Web_Set call. | |||
It is probably a good idea to set <var>NOMSGSEND</var> in the JANUS DEFINE command, then specify <code>MSGSEND</code> in the ON rules for the few URLs (in $Web_Set calls for the few applications) where it is desirable to have | It is probably a good idea to set <var>NOMSGSEND</var> in the JANUS DEFINE command, then specify <code>MSGSEND</code> in the ON rules for the few URLs (in $Web_Set calls for the few applications) where it is desirable to have <var class="product">Model 204</var> messages sent to the browser. | ||
Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | ||
== | ==See also== | ||
<ul> | |||
<li>[[List of Janus commands]] | |||
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] | |||
</ul> | |||
[[Category:JANUS DEFINE parameters|MSGSEND and NOMSGSEND]] | [[Category:JANUS DEFINE parameters|MSGSEND and NOMSGSEND]] | ||
Latest revision as of 22:18, 16 April 2013
Enable/Disable sending of 204 messages to web browser.
MSGSEND and NOMSGSEND are parameters on JANUS DEFINE, whichs define and sets characteristics of a Janus port.
Indicates whether or not Model 204 messages (as opposed to the output from PRINT or HTML statements) are to be sent to the browser.
For backward compatibility, the default for this parameter is MSGSEND, though NOMSGSEND is probably more useful for most applications.
Model 204 messages include informatory messages such as those issued when a file is opened or closed, error messages, and messages and warnings from other users sent by MSG or WARN commands. MSGSEND or NOMSGSEND can be overridden by a MSGSEND or NOMSGSEND parameter in a JANUS WEB ON rule or in a $Web_Set call.
It is probably a good idea to set NOMSGSEND in the JANUS DEFINE command, then specify MSGSEND in the ON rules for the few URLs (in $Web_Set calls for the few applications) where it is desirable to have Model 204 messages sent to the browser.
Valid only for WEBSERV ports.