WEBLOGMAX (JANUS DEFINE parameter): Difference between revisions
mNo edit summary |
m (show "JANUS DEFINE parameter" in title) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<span class="pageSubtitle">WEBLOGMAX xxxx — Max cached logins held for a single user</span> | |||
<span class="pageSubtitle" | |||
WEBLOGMAX is a parameter on | <var>WEBLOGMAX</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
This parameter indicates the maximum number of cached login sessions to be held for a single user. This parameter has no effect unless the <var>[[WEBLOGHOLD (JANUS DEFINE parameter)|WEBLOGHOLD]]</var> parameter is set to something other than 0. | This parameter indicates the maximum number of cached login sessions to be held for a single user. This parameter has no effect unless the <var>[[WEBLOGHOLD (JANUS DEFINE parameter)|WEBLOGHOLD]]</var> parameter is set to something other than 0. | ||
Since a single web page can contain many images, and since browsers often request images on a page in parallel, a single request for such a logon protected page can result in multiple simultaneous logons for the userid. Logon caching would then hold these logons, tying up several sdaemons in the process. WEBLOGMAX would prevent more than the indicated number of sdaemons to be used for a single user's requests. All login protected requests for a user are then threaded trough WEBLOGMAX users. This is generally not a problem since the typical bottleneck for most requests is network bandwidth, and multi-threading requests for a single user does not alleviate network bandwidth problems. For more discussion of the logon caching feature, see | Since a single web page can contain many images, and since browsers often request images on a page in parallel, a single request for such a logon protected page can result in multiple simultaneous logons for the userid. Logon caching would then hold these logons, tying up several sdaemons in the process. <var>WEBLOGMAX</var> would prevent more than the indicated number of sdaemons to be used for a single user's requests. All login protected requests for a user are then threaded trough <var>WEBLOGMAX</var> users. This is generally not a problem since the typical bottleneck for most requests is network bandwidth, and multi-threading requests for a single user does not alleviate network bandwidth problems. For more discussion of the logon caching feature, see [[Janus Web Server login caching]]. | ||
<var>[[WEBLM (JANUS DEFINE parameter)|WEBLM]]</var> is a synonym for WEBLOGMAX. | <var>[[WEBLM (JANUS DEFINE parameter)|WEBLM]]</var> is a synonym for <var>WEBLOGMAX</var>. | ||
Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | ||
| Line 14: | Line 13: | ||
==See also== | ==See also== | ||
<ul> | <ul> | ||
<li>[[List of Janus commands]] | <li>[[List of Janus commands]] </li> | ||
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] | <li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] </li> | ||
</ul> | </ul> | ||
[[Category:JANUS DEFINE parameters|WEBLOGMAX]] | [[Category:JANUS DEFINE parameters|WEBLOGMAX]] | ||
Latest revision as of 15:52, 23 April 2015
WEBLOGMAX xxxx — Max cached logins held for a single user
WEBLOGMAX is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
This parameter indicates the maximum number of cached login sessions to be held for a single user. This parameter has no effect unless the WEBLOGHOLD parameter is set to something other than 0.
Since a single web page can contain many images, and since browsers often request images on a page in parallel, a single request for such a logon protected page can result in multiple simultaneous logons for the userid. Logon caching would then hold these logons, tying up several sdaemons in the process. WEBLOGMAX would prevent more than the indicated number of sdaemons to be used for a single user's requests. All login protected requests for a user are then threaded trough WEBLOGMAX users. This is generally not a problem since the typical bottleneck for most requests is network bandwidth, and multi-threading requests for a single user does not alleviate network bandwidth problems. For more discussion of the logon caching feature, see Janus Web Server login caching.
WEBLM is a synonym for WEBLOGMAX.
Valid only for WEBSERV ports.