crossley 02/04/24 22:42:12
Modified: src/documentation/xdocs performancetips.xml
Log:
Fix XML validation issues: no <p> within <li>, no <note> within <p>
Revision Changes Path
1.5 +29 -28 xml-cocoon2/src/documentation/xdocs/performancetips.xml
Index: performancetips.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/performancetips.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- performancetips.xml 3 Apr 2002 19:31:33 -0000 1.4
+++ performancetips.xml 25 Apr 2002 05:42:12 -0000 1.5
@@ -17,11 +17,10 @@
<p>As in the real world, it needs some kind of evolution to get better.
If you have suggestions how to make it better or new kool tips, then be brave and
send it to the <link href="http://xml.apache.org/cocoon/mail-lists.html";>
- Cocoon Mailing Lists</link>!
+ Cocoon Mailing Lists</link>!</p>
<note>Sometimes the tips maybe doubled or contradictory. If you notice something
like that, then send a note to the <link
href="http://xml.apache.org/cocoon/mail-lists.html";>
Cocoon Mailing Lists</link>.</note>
- </p>
</s1>
<s1 title="Common">
@@ -41,9 +40,11 @@
<li>Consider prerendering or time-based batch-process the static parts
of your site. PDF reports, rasterized SVG graphs or things that change
- regularly.</li>Use a transparent proxy in front of your web server! The
fastest
+ regularly.</li>
+
+ <li>Use a transparent proxy in front of your web server! The fastest
response is the one that is not even processed. Cocoon is very slow
- (compared to a proxy server) to read resources such as stylesheets
+ (compared to a proxy server) to read resources such as stylesheets</li>
<li>For optimum performance with Tomcat 4 and Cocoon 2,
use the HTTP/1.0 connector.</li>
@@ -86,9 +87,10 @@
better performance each time you request it. However, if your cache is set
too small to keep the entire XML in memory, the cache will be of no
benefit.</li>
- <li>Watch the cachability in the log files, and make sure that things are
being fed from the
- cache. <note>Only use dynamic data when it is needed. Dynamic pages can't be
cached 100%.
- </note></li>
+ <li>Watch the cachability in the log files, and make sure that things
+ are being fed from the cache.</li>
+ <li>Only use dynamic data when it is needed. Dynamic pages can't be
+ cached 100%.</li>
</ul>
</s1>
@@ -116,18 +118,18 @@
</s1>
<s1 title="Perfomance Formulas">
- <ul>g
- <li>Consider following formula for Pipeline Processing:
- <p><code>Number_of_simultaneous_users * depth_of_content_aggregation</code></p>
+ <ul>
+ <li>Consider following formula for Pipeline Processing:<br />
+ <code>Number_of_simultaneous_users * depth_of_content_aggregation</code>
</li>
- <li>Consider following formula for Generators/Transformers/Serializers:
- <p><code>Amount_required_to_process_one_request *
Number_of_simultaneous_users</code></p>
+ <li>Consider following formula for Generators/Transformers/Serializers:<br />
+ <code>Amount_required_to_process_one_request *
Number_of_simultaneous_users</code>
</li>
- <li>Consider following formula for Connectors:
- <p><code>Count_of_pipeline_components_to_process_one_request *
- Number_of_simultaneous_users</code></p></li>
+ <li>Consider following formula for Connectors:<br />
+ <code>Count_of_pipeline_components_to_process_one_request *
+ Number_of_simultaneous_users</code></li>
</ul>
</s1>
@@ -142,23 +144,22 @@
</s1>
<s1 title="XSP">
- <ul>
- <li><p>Consider turning your XSPs into Generators by hand and call them
- directly. Of course you don't need to do this for all pages, but it's
- recommended to it for those which are heavy loaded.</p>
- <p>You can try it this way:</p>
- <p>Cocoon will compile your XSP's into Java classes
- (see tomcat/work/..../org/apache/cocoon/www/my_xsp.class). After that, add
- the generated Generator to the Sitemap:</p>
+ <p>Consider turning your XSPs into Generators by hand and call them
+ directly. Of course you don't need to do this for all pages, but it's
+ recommended to it for those which are heavy loaded.</p>
+ <p>You can try it this way:</p>
+ <p>Cocoon will compile your XSP's into Java classes
+ (see tomcat/work/..../org/apache/cocoon/www/my_xsp.class). After that, add
+ the generated Generator to the Sitemap:<br />
<code>
- <map:generator type="myXSP" src="org.apache.cocoon.www.my_xsp"/>
+ <map:generator type="myXSP" src="org.apache.cocoon.www.my_xsp"/>
</code>
- <p>And use it:</p>
+ </p>
+ <p>And use it:<br />
<code>
- <map:generate type="myXSP"/>
+ <map:generate type="myXSP"/>
</code>
- </li>
- </ul>
+ </p>
</s1>
<s1 title="XSLT and XSL">
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
