X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=doc%2Fthreads.html;h=f7ac957f1b603cdcbaa6cd0592f82b0d450caad9;hb=refs%2Fchanges%2F17%2F75517%2F1;hp=d206f5433e9815ffd9a3e27a22e5987c61222cb2;hpb=7714ab7384828d6cda6f950a8d789ee36ca62452;p=platform%2Fupstream%2Flibxml2.git
diff --git a/doc/threads.html b/doc/threads.html
index d206f54..f7ac957 100644
--- a/doc/threads.html
+++ b/doc/threads.html
@@ -9,13 +9,15 @@ H3 {font-family: Verdana,Arial,Helvetica}
A:link, A:visited, A:active { text-decoration: underline }
Thread safety![Action against software patents](epatents.png) | ![Gnome2 Logo](gnome2.png) ![W3C Logo](w3c.png) ![Red Hat Logo](redhat.gif) | The XML C parser and toolkit of GnomeThread safety |
|
|
| Starting with 2.4.7, libxml2 makes provisions to ensure that concurrent
threads can safely work in parallel parsing different documents. There is
-however a couple of things to do to ensure it: - configure the library accordingly using the --with-threads options
+however a couple of things to do to ensure it:
+ - configure the library accordingly using the --with-threads options
- call xmlInitParser() in the "main" thread before using any of the
libxml2 API (except possibly selecting a different memory allocator)
Note that the thread safety cannot be ensured for multiple threads sharing
the same document, the locking must be done at the application level, libxml
exports a basic mutex and reentrant mutexes API in <libxml/threads.h>.
-The parts of the library checked for thread safety are: - concurrent loading
+The parts of the library checked for thread safety are:
+ - concurrent loading
- file access resolution
- catalog access
- catalog building
|
|
|
|
|