O
Ola Natvig
Anybody out there who knows if the 4suite implementation of XSLT are a
threadsafe one?
threadsafe one?
Ola said:Anybody out there who knows if the 4suite implementation of XSLT are a
threadsafe one?
Diez said:Ola Natvig wrote:
What do you mean by that? You can of course transform xml using xslt in as
many threads as you like - but what do you want with two or more threads in
_one_ transformation? You start it, and some time later the result is
there.
Diez said:What do you mean by that? You can of course transform xml using xslt in as
many threads as you like
Istvan said:It is not unthinkable that some parts of the library would not be
threadsafe. They could have some internal shared global variable
that keeps track of an intermediate state.
Some C string processing functions are not thread safe either.
Istvan.
threadsafe. They could have some internal shared global variable
that keeps track of an intermediate state.
Some C string processing functions are not thread safe either.
transformation process and another one starts processing on the same
processor will this work?
Will the half-way finished thread be in the way of the one starting the
processing before the stoped thread are done.
I think that's what I ment. Can a XSLT processor object be shared
between multiple threads?
this is not the case - modern OO-style apis associate state usually on a
per-object base. And 4suite is heavily OO-styled.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.