hgomez 2004/02/16 00:16:58 Modified: jk/xdocs/jk2 configwebcom.xml Log: correct documentation, lb_factor instead of lbfactor.
Fix Bug #26674 Revision Changes Path 1.10 +7 -7 jakarta-tomcat-connectors/jk/xdocs/jk2/configwebcom.xml Index: configwebcom.xml =================================================================== RCS file: /home/cvs/jakarta-tomcat-connectors/jk/xdocs/jk2/configwebcom.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- configwebcom.xml 16 May 2003 10:28:44 -0000 1.9 +++ configwebcom.xml 16 Feb 2004 08:16:58 -0000 1.10 @@ -295,7 +295,7 @@ <td>? </td> </tr> <tr> - <td>lbfactor</td> + <td>lb_factor</td> <td>1</td> <td> Load balancing factor to use. At this moment, it'll be set on the worker, @@ -360,7 +360,7 @@ <td>If set to 1 Disables the Nagle algorithm for send coalescing</td> </tr> <tr> - <td>lbfactor</td> + <td>lb_factor</td> <td>1</td> <td> Load balancing factor to use. At this moment, it'll be set on the worker, @@ -464,10 +464,10 @@ <tr> <td>max_connections</td> <td>0 (unlimited)</td> - <td>Maximum number of currently used endpoints. - If the specified number is reached then the load balancer has the chance - to try another worker. This is very useful in situations when having multiple - servers and you wish to finer grade the lb_factor. + <td>Maximum number of currently used endpoints. + If the specified number is reached then the load balancer has the chance + to try another worker. This is very useful in situations when having multiple + servers and you wish to finer grade the lb_factor. </td> </tr> </table> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]