Re: [xml] libxml2 thread safety

On Tue, Oct 02, 2001 at 01:47:02PM -0400, Jon Smirl wrote:
Currently Xerces and Xalan have a single static initialization which needs
to be thread safe. All other global information it is stored in processor
objects which are private to a thread.

  Sounds the right approach, I also think the way that mapping is done
should be left to some user code (with possibly a couple of examples for
most common schemes and thread APIs).

In general adding thread safety was a very bad experience on Xerces/Xalan.
This is much better handled at a higher level.

  Basically agree, if someone needs thread safe operations at the DOM
(i.e. tree access level) then they are better served anyway by doing the
synchronization more globally before entering the library code.


Daniel Veillard      | Red Hat Network
veillard redhat com  | libxml Gnome XML XSLT toolkit | Rpmfind RPM search engine

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]