You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by el...@apache.org on 2001/10/29 19:35:09 UTC
cvs commit: xml-xerces/java/docs faq-pcfp.xml faq-performance.xml
elena 01/10/29 10:35:09
Modified: java/docs faq-pcfp.xml faq-performance.xml
Log:
update docs
Revision Changes Path
1.2 +3 -4 xml-xerces/java/docs/faq-pcfp.xml
Index: faq-pcfp.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-pcfp.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- faq-pcfp.xml 2001/10/25 20:19:36 1.1
+++ faq-pcfp.xml 2001/10/29 18:35:09 1.2
@@ -7,20 +7,19 @@
<p>
If a validator is included in the pipeline, assessment is
done, whether the validation feature is set to true or false.
- Currently, validation only enables the reporting of error
- messages. This behaviour may be revisited/changed in the future.
+ Currently, validation only enables the validation constraint error reporting. The validation feature does not control the infoset augmentation: if a validator is included in the pipeline the parser will augment the infoset according to the grammar specified for the instance document. This behaviour may be revisited/changed in the future.
</p>
</a>
</faq>
<faq title='Default Parser Configuration'>
- <q>What vaidation behavior do I expect from the default parser configuration?</q>
+ <q>What validation behavior do I expect from the default parser configuration?</q>
<a>
<p>
The default configuration includes both DTD validator and XML
schema validator, so it's capable of validating an instance
against both kinds of grammars. But this could bring some
performance hit for those applications that only process XML
- documents with DTD. If you cares about performance, and only
+ documents with DTD. If you care about performance, and only
use DTD, please use DTD configuration instead.
</p>
</a>
1.4 +12 -5 xml-xerces/java/docs/faq-performance.xml
Index: faq-performance.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-performance.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq-performance.xml 2001/08/23 00:35:14 1.3
+++ faq-performance.xml 2001/10/29 18:35:09 1.4
@@ -20,6 +20,11 @@
instances. A pool of reusable parser instances might be a good idea
if you have multiple threads parsing at the same time.
</p>
+ <p>
+ The parser configuration will affect the performance of the parser.
+ If you are interested in evaluating the parser performance with DTDs use StandardParserConfiguration.
+ For testing the performance for XML Schema evaluation use DTDXSParserConfiguration (Note: this is the default parser configuration).
+ </p>
</a>
</faq>
<faq title='Parsing Documents Performance'>
@@ -69,11 +74,13 @@
<q>XML Application Performance</q>
<a>
<ul>
- <li>
- Turn validation off if you don't need it. Validation is expensive.
- Also, avoid using a DOCTYPE line in your XML document. The current
- version of the parser will always read the DTD if the DOCTYPE line
- is specified even when not validating.
+ <li>If you don't need validation (and infoset augmentation) of XML documents, don't include validators (DTD or XML Schema) in the pipeline. Including the validator components in the pipeline will result in a performance hit for your application: if a validator component is present in the pipeline, Xerces will try to validate and augment the infoset even if the validation feature is set to false.
+ If you are only interested in validating against DTDs don't include XML Schema validator in the pipeline, instead use StandardParserConfiguration.
+
+ </li>
+ <li> If you don't need validation, avoid using a DOCTYPE line in your XML document.
+ The current version of the parser will always read the DTD if the DOCTYPE line
+ is specified even when validation feature is set to false.
</li>
<li>
For large documents, avoid using DOM which uses a lot of memory.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-cvs-help@xml.apache.org