Re: [xslt] "libxslt with thread-enabled libxml2?"
- From: Igor Zlatkovic <igor zlatkovic com>
- To: xslt gnome org
- Subject: Re: [xslt] "libxslt with thread-enabled libxml2?"
- Date: Fri, 11 Apr 2003 23:02:25 +0200
On Fri, Apr 11, 2003 at 02:57:42PM -0400, Daniel Veillard wrote:
> Hum, could you be more precise if something is needed at the code level.
> I expect to switch libxml2 compilation to be thread aware on Linux
> (now that some performances problems with memory allocation when compiling
> with threads have been addressed). So if libxslt needs work I'm interested
> of getting your advice :-)
Well, I guess libxslt will need the same protection libxml allready has.
Imagine ten threads applying the same stylesheet on ten different
documents. Each thread has its own vision of what, say, xsltGenericError
or xsltMaxDepth should contain and start setting and resetting these at
the whim of the kernel scheduler. I have never tested it, but that
doesn't sound good to me :-)
That aside, I strongly believe that thread sync on that level should be
left to the application code. Neither libxml nor libxslt can ever know
what an application will do with them.
Libxml and libxslt don't need or use asynchronous processing, like I
call some function implemented in these and do other work until I
receive a notification about the results. As long this remains that way,
I would leave thread sync to the applications, there is no better place
] [Thread Prev