You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by mt...@apache.org on 2004/11/27 14:38:48 UTC
svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Author: mturk
Date: Sat Nov 27 05:38:47 2004
New Revision: 106707
URL: http://svn.apache.org/viewcvs?view=rev&rev=106707
Log:
Add desription for schedlurer algo and
balancer manager
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en
httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en
Url: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en?view=diff&rev=106707&p1=httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en&r1=106706&p2=httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en&r2=106707
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en Sat Nov 27 05:38:47 2004
@@ -49,11 +49,202 @@
<div id="quickview"><h3 class="directives">Directives</h3>
<p>This module provides no
directives.</p>
-<h3>See also</h3>
+<h3>Topics</h3>
+<ul id="topics">
+<li><img alt="" src="../images/down.gif" /> <a href="#scheduler">Load balancer scheduler algorithm</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#enable">Enabling Balancer Manager Support</a></li>
+</ul><h3>See also</h3>
<ul class="seealso">
<li><code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code></li>
</ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="scheduler" id="scheduler">Load balancer scheduler algorithm</a></h2>
+
+ <p>The idea behind this scheduler is the following:</p>
+ <p><strong>lbfactor</strong> is <em>how much we expect this worker
+ to work</em>, or <em>the workers's work quota</em>.</p>
+ <p><strong>lbstatus</strong> is <em>how urgent this worker has to work
+ to fulfill its quota of work</em>.</p>
+ <p>The <strong>worker</strong> is a member of the load balancer,
+ usually a remote host serving one of the supported protocols</p>
+ <p>We distribute each worker's work quota to the worker, and then look
+ which of them needs to work most urgently (biggest lbstatus). This
+ worker is then selected for work, and its lbstatus reduced by the
+ total work quota we distributed to all workers. Thus the sum of all
+ lbstatus does not change.(*)</p>
+ <p>If some workers are disabled, the others will
+ still be scheduled correctly.</p>
+ <p>If a balancer is configured as follows:</p>
+
+
+<code>
+ <table>
+ <tr>
+ <td width="80">worker</td>
+ <td width="30" style="text-align: right;">a</td>
+ <td width="30" style="text-align: right;">b</td>
+ <td width="30" style="text-align: right;">c</td>
+ <td width="30" style="text-align: right;">d</td>
+ </tr>
+ <tr>
+ <td>lbfactor</td>
+ <td style="text-align: right;">25</td>
+ <td style="text-align: right;">25</td>
+ <td style="text-align: right;">25</td>
+ <td style="text-align: right;">25</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ </tr>
+ </table>
+</code>
+ <p>And b gets disabled, the following schedule is produced:</p>
+<code>
+ <table>
+ <tr>
+ <td width="80">lbstatus</td>
+ <td width="30" style="text-align: right;">-50</td>
+ <td width="30" style="text-align: right;">0</td>
+ <td width="30" style="text-align: right;">25</td>
+ <td width="30" style="text-align: right;">25</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-25</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">-25</td>
+ <td style="text-align: right;">50</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ </tr>
+ <tr>
+ <td colspan="5">(repeat)</td>
+ </tr>
+ </table>
+</code>
+ <p>That is it schedules: a c d a c d a c d ...</p>
+ <p>The following asymmetric configuration works as one would expect:</p>
+<code>
+ <table>
+ <tr>
+ <td width="80">worker</td>
+ <td width="30" style="text-align: right;">a</td>
+ <td width="30" style="text-align: right;">b</td>
+ </tr>
+ <tr>
+ <td>lbfactor</td>
+ <td style="text-align: right;">70</td>
+ <td style="text-align: right;">30</td>
+ </tr>
+ <tr>
+ <td colspan="3"> </td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-30</td>
+ <td style="text-align: right;">30</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">40</td>
+ <td style="text-align: right;">-40</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">10</td>
+ <td style="text-align: right;">-10</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-20</td>
+ <td style="text-align: right;">20</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-50</td>
+ <td style="text-align: right;">50</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">20</td>
+ <td style="text-align: right;">-20</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-10</td>
+ <td style="text-align: right;">10</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-40</td>
+ <td style="text-align: right;">40</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">30</td>
+ <td style="text-align: right;">-30</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ </tr>
+ <tr>
+ <td colspan="3">(repeat)</td>
+ </tr>
+ </table>
+</code>
+
+ <p>That is after 10 schedules, the schedule repeats and 7 a are selected
+ with 3 b interspersed.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="enable" id="enable">Enabling Balancer Manager Support</a></h2>
+
+ <p>Balancer manager enables dynamic update of balancer
+ members. You can use balancer manager to change the balace
+ factor or a particular member, or put it in the off line
+ mode.</p>
+ <p>This module <em>requires</em> the service of
+ <code class="module"><a href="../mod/mod_status.html">mod_status</a></code>.
+ Balancer manager enables dynamic update of balancer
+ members. You can use balancer manager to change the balace
+ factor or a particular member, or put it in the off line
+ mode.
+ </p>
+
+ <p>Thus, in order to get the ability of load balancer management,
+ <code class="module"><a href="../mod/mod_status.html">mod_status</a></code> and <code class="module"><a href="../mod/mod_proxy_balancer.html">mod_proxy_balancer</a></code>
+ have to be present in the server.</p>
+
+ <p>To enable load balancer management for browsers from the foo.com
+ domain add this code to your <code>httpd.conf</code>
+ configuration file</p>
+<div class="example"><p><code>
+ <Location /balancer-manager><br />
+ SetHandler balancer-manager<br />
+<br />
+ Order Deny,Allow<br />
+ Deny from all<br />
+ Allow from .foo.com<br />
+ </Location>
+</code></p></div>
+
+ <p>You can now access load balancer manager by using a Web browser
+ to access the page
+ <code>http://your.server.name/balancer-manager</code></p>
+</div>
</div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="../en/mod/mod_proxy_balancer.html" title="English"> en </a> |
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Url: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml?view=diff&rev=106707&p1=httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml&r1=106706&p2=httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml&r2=106707
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml Sat Nov 27 05:38:47 2004
@@ -48,4 +48,191 @@
</summary>
<seealso><module>mod_proxy</module></seealso>
+<section id="scheduler">
+ <title>Load balancer scheduler algorithm</title>
+ <p>The idea behind this scheduler is the following:</p>
+ <p><strong>lbfactor</strong> is <em>how much we expect this worker
+ to work</em>, or <em>the workers's work quota</em>.</p>
+ <p><strong>lbstatus</strong> is <em>how urgent this worker has to work
+ to fulfill its quota of work</em>.</p>
+ <p>The <strong>worker</strong> is a member of the load balancer,
+ usually a remote host serving one of the supported protocols</p>
+ <p>We distribute each worker's work quota to the worker, and then look
+ which of them needs to work most urgently (biggest lbstatus). This
+ worker is then selected for work, and its lbstatus reduced by the
+ total work quota we distributed to all workers. Thus the sum of all
+ lbstatus does not change.(*)</p>
+ <p>If some workers are disabled, the others will
+ still be scheduled correctly.</p>
+ <p>If a balancer is configured as follows:</p>
+
+ <!-- Very ugly, but i can not make the table right aligned -->
+<code>
+ <table>
+ <tr>
+ <td width="80">worker</td>
+ <td width="30" style="text-align: right;">a</td>
+ <td width="30" style="text-align: right;">b</td>
+ <td width="30" style="text-align: right;">c</td>
+ <td width="30" style="text-align: right;">d</td>
+ </tr>
+ <tr>
+ <td>lbfactor</td>
+ <td style="text-align: right;">25</td>
+ <td style="text-align: right;">25</td>
+ <td style="text-align: right;">25</td>
+ <td style="text-align: right;">25</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ </tr>
+
+ </table>
+</code>
+ <p>And b gets disabled, the following schedule is produced:</p>
+<code>
+ <table>
+ <tr>
+ <td width="80">lbstatus</td>
+ <td width="30" style="text-align: right;">-50</td>
+ <td width="30" style="text-align: right;">0</td>
+ <td width="30" style="text-align: right;">25</td>
+ <td width="30" style="text-align: right;">25</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-25</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">-25</td>
+ <td style="text-align: right;">50</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ </tr>
+ <tr>
+ <td colspan="5">(repeat)</td>
+ </tr>
+ </table>
+</code>
+ <p>That is it schedules: a c d a c d a c d ...</p>
+ <p>The following asymmetric configuration works as one would expect:</p>
+<code>
+ <table>
+ <tr>
+ <td width="80">worker</td>
+ <td width="30" style="text-align: right;">a</td>
+ <td width="30" style="text-align: right;">b</td>
+ </tr>
+ <tr>
+ <td>lbfactor</td>
+ <td style="text-align: right;">70</td>
+ <td style="text-align: right;">30</td>
+ </tr>
+ <tr>
+ <td colspan="3"> </td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-30</td>
+ <td style="text-align: right;">30</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">40</td>
+ <td style="text-align: right;">-40</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">10</td>
+ <td style="text-align: right;">-10</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-20</td>
+ <td style="text-align: right;">20</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-50</td>
+ <td style="text-align: right;">50</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">20</td>
+ <td style="text-align: right;">-20</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-10</td>
+ <td style="text-align: right;">10</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">-40</td>
+ <td style="text-align: right;">40</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">30</td>
+ <td style="text-align: right;">-30</td>
+ </tr>
+ <tr>
+ <td>lbstatus</td>
+ <td style="text-align: right;">0</td>
+ <td style="text-align: right;">0</td>
+ </tr>
+ <tr>
+ <td colspan="3">(repeat)</td>
+ </tr>
+ </table>
+</code>
+
+ <p>That is after 10 schedules, the schedule repeats and 7 a are selected
+ with 3 b interspersed.</p>
+</section>
+
+<section id="enable">
+ <title>Enabling Balancer Manager Support</title>
+ <p>Balancer manager enables dynamic update of balancer
+ members. You can use balancer manager to change the balace
+ factor or a particular member, or put it in the off line
+ mode.</p>
+ <p>This module <em>requires</em> the service of
+ <module>mod_status</module>.
+ Balancer manager enables dynamic update of balancer
+ members. You can use balancer manager to change the balace
+ factor or a particular member, or put it in the off line
+ mode.
+ </p>
+
+ <p>Thus, in order to get the ability of load balancer management,
+ <module>mod_status</module> and <module>mod_proxy_balancer</module>
+ have to be present in the server.</p>
+
+ <p>To enable load balancer management for browsers from the foo.com
+ domain add this code to your <code>httpd.conf</code>
+ configuration file</p>
+<example>
+ <Location /balancer-manager><br />
+ SetHandler balancer-manager<br />
+<br />
+ Order Deny,Allow<br />
+ Deny from all<br />
+ Allow from .foo.com<br />
+ </Location>
+</example>
+
+ <p>You can now access load balancer manager by using a Web browser
+ to access the page
+ <code>http://your.server.name/balancer-manager</code></p>
+</section>
+
</modulesynopsis>
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by André Malo <nd...@perlig.de>.
* Mladen Turk wrote:
> Astrid Keßler wrote:
> > Mladen, I think there is a big misunderstanding about the docs, the
> > xml-files and the build process. We do _not_ style our documents
> > graphically when writing the xml documents. We only write content.
> > Layout is done during the build process. And it is done globally for
> > the whole domument.
> >
> > What you did here - with best intention, sure - is trying to force a
> > specific layout by breaking semantics. Please don't do this. Don't try
> > to outwit the build process.
> > If you don't like the layout, then this is worth a discusion. Suggest a
> > better layout. But please, don't do such tricky things.
>
> Well, take a look at ssl. I didn't do nothing more.
These huge <pre> sections in mod_ssl docs are a bad example, because they're
simply not revised yet. I'm wondering why I've spent my evening with saying
"Please ask if you don't know" all the time. *sigh*
> And once again. Those are *not* tables with some data,
> but rather formated code. It only happens that they looks like tables.
There's no code. It's just a table of values. Or wouldn't you say, that
a b c d e
/--------------
x | 0 1 2 3 4
y | 0 1 4 9 16
is a table? Try a voice browser. *I* would give up after listening to the
first line.
nd
--
"Solides und umfangreiches Buch"
-- aus einer Rezension
<http://pub.perlig.de/books.html#apache2>
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en
/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by Mladen Turk <mt...@apache.org>.
Astrid Keßler wrote:
>>Well, take a look at ssl. I didn't do nothing more.
>
>
> Ah, well, there are still some old code examples not correct yet. Did
> you really choose these cases as an example? Sorry, this is old and will
> be changed.
>
>
>>And once again. Those are *not* tables with some data,
>>but rather formated code. It only happens that they looks like tables.
>
>
> This is code? Uhm, where do I have to put this code in?
>
> And another question. You wrote:
> "Thus the sum of all lbstatus does not change.(*)"
> What does (*) mean?
>
Something like book foot note that will point to a detailed
description when it can change. Not sure if this is a
right way to write that.
Anyhow it should contain the following at the end of
the topic:
(*) The sum of all lbfactors can change if the worker gets
unusable either by going to an error state or disabled
manually by load balancer manager. Load balancer will
periodically check for all workers that are in the error
state and try to recover them, thus updating the sum of
lbfactors.
--
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by Astrid Keßler <ke...@kess-net.de>.
> Well, take a look at ssl. I didn't do nothing more.
Ah, well, there are still some old code examples not correct yet. Did
you really choose these cases as an example? Sorry, this is old and will
be changed.
> And once again. Those are *not* tables with some data,
> but rather formated code. It only happens that they looks like tables.
This is code? Uhm, where do I have to put this code in?
And another question. You wrote:
"Thus the sum of all lbstatus does not change.(*)"
What does (*) mean?
> But OK, if you think that this would be better done trough tables,
> it's fine with me.
I still think so ;)
And the for the last code example at the bottom I suggest to use
<example> and <indent>.
Kess
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en
/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by Mladen Turk <mt...@apache.org>.
Astrid Keßler wrote:
>
> Mladen, I think there is a big misunderstanding about the docs, the
> xml-files and the build process. We do _not_ style our documents
> graphically when writing the xml documents. We only write content.
> Layout is done during the build process. And it is done globally for the
> whole domument.
>
> What you did here - with best intention, sure - is trying to force a
> specific layout by breaking semantics. Please don't do this. Don't try
> to outwit the build process.
> If you don't like the layout, then this is worth a discusion. Suggest a
> better layout. But please, don't do such tricky things.
>
Well, take a look at ssl. I didn't do nothing more.
And once again. Those are *not* tables with some data,
but rather formated code. It only happens that they looks like tables.
But OK, if you think that this would be better done trough tables,
it's fine with me.
--
MT.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by Astrid Keßler <ke...@kess-net.de>.
>>>>>Also that was my original intention (have no idea why I used tables
>>>>>for that).
Because you are on the right way? ;)
>>>>It appears to be tabular data, so a table is the perfect thing to use.
>>>>It clearly states, what these text snippets belong to (table header,
>>>>table data).
>>>
>>>OK then :).
>>>
>>>But I don't like the <th> entries in the table like you implemented.
>>>The bolded should be the number in the coulumn of the worker that
>>>is currently scheduled (If you wish you can patch that, the patch
>>>is in the attachment).
>>
>>
>> Uuh. I think, you've misunderstood some stuff ;-). You're confusing layout
>> and content a bit.
>>
> Well, I have committed how they should look. They are not real tables,
> but rather p code, only in the table form.
Mladen, I think there is a big misunderstanding about the docs, the
xml-files and the build process. We do _not_ style our documents
graphically when writing the xml documents. We only write content.
Layout is done during the build process. And it is done globally for the
whole domument.
What you did here - with best intention, sure - is trying to force a
specific layout by breaking semantics. Please don't do this. Don't try
to outwit the build process.
If you don't like the layout, then this is worth a discusion. Suggest a
better layout. But please, don't do such tricky things.
Kess
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en
/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by Mladen Turk <mt...@apache.org>.
André Malo wrote:
> * Mladen Turk wrote:
>
>
>>Well, I have committed how they should look. They are not real tables,
>>but rather p code, only in the table form.
>
>
> Okay, I'll try it in more simple words: Just don't care about how it will
> look. If you're writing XML content, there's no layout, just markup.
>
> I'm going to fix it again (and hopefully finally).
>
Perhaps inside <example>. Those are really not tables,
but rather formated code, although they look like tables.
--
MT.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by André Malo <nd...@perlig.de>.
* Mladen Turk wrote:
> Well, I have committed how they should look. They are not real tables,
> but rather p code, only in the table form.
Okay, I'll try it in more simple words: Just don't care about how it will
look. If you're writing XML content, there's no layout, just markup.
I'm going to fix it again (and hopefully finally).
nd
--
"Das Verhalten von Gates hatte mir bewiesen, dass ich auf ihn und seine
beiden Gefährten nicht zu zählen brauchte" -- Karl May, "Winnetou III"
Im Westen was neues: <http://pub.perlig.de/books.html#apache2>
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en
/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by Mladen Turk <mt...@apache.org>.
André Malo wrote:
> * Mladen Turk wrote:
>
>
>>André Malo wrote:
>>
>>>* Mladen Turk wrote:
>>>
>>>>Also that was my original intention (have no idea why I used tables
>>>>for that).
>>>
>>>It appears to be tabular data, so a table is the perfect thing to use.
>>>It clearly states, what these text snippets belong to (table header,
>>>table data).
>>
>>OK then :).
>>
>>But I don't like the <th> entries in the table like you implemented.
>>The bolded should be the number in the coulumn of the worker that
>>is currently scheduled (If you wish you can patch that, the patch
>>is in the attachment).
>
>
> Uuh. I think, you've misunderstood some stuff ;-). You're confusing layout
> and content a bit.
>
Well, I have committed how they should look. They are not real tables,
but rather p code, only in the table form.
--
MT.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by André Malo <nd...@perlig.de>.
* Mladen Turk wrote:
> André Malo wrote:
> > * Mladen Turk wrote:
> >>Also that was my original intention (have no idea why I used tables
> >>for that).
> >
> > It appears to be tabular data, so a table is the perfect thing to use.
> > It clearly states, what these text snippets belong to (table header,
> > table data).
>
> OK then :).
>
> But I don't like the <th> entries in the table like you implemented.
> The bolded should be the number in the coulumn of the worker that
> is currently scheduled (If you wish you can patch that, the patch
> is in the attachment).
Uuh. I think, you've misunderstood some stuff ;-). You're confusing layout
and content a bit.
<th> stands for "table header" and means "this cell describes the
accompanying column or row". Those are bold all over the docs. But we could
enclose the values, which should be highlighted in <strong> or <em>. How
does this sound?
(strong appears bold in graphical browsers, em italic).
Alternatively we could add another background color to the layout for such
purposes.
nd
--
"Das Verhalten von Gates hatte mir bewiesen, dass ich auf ihn und seine
beiden Gefährten nicht zu zählen brauchte" -- Karl May, "Winnetou III"
Im Westen was neues: <http://pub.perlig.de/books.html#apache2>
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en
/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by Mladen Turk <mt...@apache.org>.
André Malo wrote:
> * Mladen Turk wrote:
>
>
>
>>Also that was my original intention (have no idea why I used tables
>>for that).
>
>
> It appears to be tabular data, so a table is the perfect thing to use.
> It clearly states, what these text snippets belong to (table header, table
> data).
>
OK then :).
But I don't like the <th> entries in the table like you implemented.
The bolded should be the number in the coulumn of the worker that
is currently scheduled (If you wish you can patch that, the patch
is in the attachment).
--
MT.
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by André Malo <nd...@perlig.de>.
* Mladen Turk wrote:
> I didn't know it's discouraged.
> For example:
>
> <code>
> <pre>
> worker a b c d
> lbfactor 25 25 25 25
> lbstatus 0 0 0 0
> </pre>
> </code>
Well, that's syntactically invalid, because <code> is an inline element,
while <pre> is a block element. The nesting you've used is neither in
(X)HTML nor in our DTD valid. You can validate the XML stuff with `build
validate-xml`. If you wanna use <code>, you'd have to put it inside <pre>.
Additionally it's semantically invalid, simply because there's no code
(*and* it's not preformatted text in that sense, it's ... a table ;-).
> Also that was my original intention (have no idea why I used tables
> for that).
It appears to be tabular data, so a table is the perfect thing to use.
It clearly states, what these text snippets belong to (table header, table
data).
nd
--
Gefunden auf einer "Webdesigner"-Seite:
> Programmierung in HTML, XML, WML, CGI, FLASH <
# André Malo # http://www.perlig.de/ #
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en
/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by Mladen Turk <mt...@apache.org>.
André Malo wrote:
> * Mladen Turk wrote:
>
>
>>What about adding <pre> to <code> rendering, or another tag that will
>>render the text as typed in, so that both spaces and carriage
>>returns are preserved?
>
>
>>Perhaps a new tag named <source> (we are using something similar on
>>jakarta), that will have the style like <code> but withing <pre></pre>?
>
>
> There's <example> for that. <pre> is also possible (also within <example>),
> but discouraged, because of its bad layout behaviour. Indentations within
> example can be done with <indent>.
>
I didn't know it's discouraged.
For example:
<code>
<pre>
worker a b c d
lbfactor 25 25 25 25
lbstatus 0 0 0 0
</pre>
</code>
Also that was my original intention (have no idea why I used tables
for that).
--
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by André Malo <nd...@perlig.de>.
* Mladen Turk wrote:
> What about adding <pre> to <code> rendering, or another tag that will
> render the text as typed in, so that both spaces and carriage
> returns are preserved?
> Perhaps a new tag named <source> (we are using something similar on
> jakarta), that will have the style like <code> but withing <pre></pre>?
There's <example> for that. <pre> is also possible (also within <example>),
but discouraged, because of its bad layout behaviour. Indentations within
example can be done with <indent>.
> This way all those tables could be omitted or need to end the line with
> <br />.
Sure, but these *are* tables (semantically). In the meantime syntactially
correct as well ;)
nd
--
Das einzige, das einen Gebäudekollaps (oder auch einen
thermonuklearen Krieg) unbeschadet übersteht, sind Kakerlaken
und AOL-CDs.
-- Bastian Lipp in dcsm
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en
/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by Mladen Turk <mt...@apache.org>.
André Malo wrote:
> * mturk@apache.org wrote:
>
>
>>+ <!-- Very ugly, but i can not make the table right aligned -->
>>+<code>
>>+ <table>
>>+ <tr>
>>+ <td width="80">worker</td>
>>+ <td width="30" style="text-align: right;">a</td>
>
>
> Mladen,
>
> I find it very well, that you're concerned about the documentation, but,
> please, if you don't know, how to write valid XML/HTML or how to achieve
> particular features, just ask here. We'll find a way to extend the system
> properly.
>
OK.
What about adding <pre> to <code> rendering, or another tag that will
render the text as typed in, so that both spaces and carriage
returns are preserved?
Perhaps a new tag named <source> (we are using something similar on
jakarta), that will have the style like <code> but withing <pre></pre>?
This way all those tables could be omitted or need to end the line with
<br />.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r106707 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.html.en /httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
Posted by André Malo <nd...@perlig.de>.
* mturk@apache.org wrote:
> + <!-- Very ugly, but i can not make the table right aligned -->
> +<code>
> + <table>
> + <tr>
> + <td width="80">worker</td>
> + <td width="30" style="text-align: right;">a</td>
Mladen,
I find it very well, that you're concerned about the documentation, but,
please, if you don't know, how to write valid XML/HTML or how to achieve
particular features, just ask here. We'll find a way to extend the system
properly.
nd
--
Das einzige, das einen Gebäudekollaps (oder auch einen
thermonuklearen Krieg) unbeschadet übersteht, sind Kakerlaken
und AOL-CDs.
-- Bastian Lipp in dcsm
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org