MSGSEND and NOMSGSEND (JANUS DEFINE parameters): Difference between revisions
m (1 revision) |
mNo edit summary |
||
| Line 14: | Line 14: | ||
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]] | ||
Revision as of 23:34, 28 February 2012
<section begin="desc" />Enable/Disable sending of 204 messages to web browser.<section end="desc" />
MSGSEND and NOMSGSEND are parameters on JANUS DEFINE, whichs define and sets characteristics of a Janus port. See the List of JANUS DEFINE parameters.
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.