Thank you very much, gentelmen.
I'm happy for now, I guess. I do undestand perl threading issue, my
problem was rather on how mod_perl and apache thread work together. I'm
quite satisfied with your explanations. Thanks a lot.
Pavel
P.S.: Stas, ... yes I saw many segfaults... :)
Perrin
Hello all,
currently I'm working over XML::Sablotron module, bringing it alive in
the multithreaded environment. I searched both of Apache and mod_perl
documentation, but there is one issue, I do not understand.
Is there some relation between Perl threads and Apache threads? What I
mean: If
Pavel Hlavnicka wrote:
Is there some relation between Perl threads and Apache threads? What I
mean: If Apache fires a new thread, what happens in mod_perl? Are perl
structures copied from the parent thread interpreter to the new one?
... or is the new perl environment clean?
Have you read this?
Oops, I overlooked the forst reading. Sorry for this.
Anyway, even after reading this, I'm not really sure, what may happen.
Is it possible, that some new interpreter is cloned later then the pool
is created, and is it possible, that ANY interpreter cloning will clone
my global data? (I really
[ Please keep posts on the list. I am not the most knowledgeable person
here about threads, mp2, or XS code. ]
Pavel Hlavnicka wrote:
Thanks again,
I'm solving following problem: generally may happen, that somebody has
an instance of XML::Sablotron (and of few more packages) allocated in
the
I'm solving following problem: generally may happen, that somebody has
an instance of XML::Sablotron (and of few more packages) allocated in
the interperter at the time, the perl is cloned.
Sablotron objects are just wrappers around internal c++ structures,
and the only data, they keep, are
