Torsten Curdt wrote:
> On Sun, 27 Jan 2002, Vadim Gritsenko wrote:
>
>
>>Hi,
>>
>>I though somebody might be interested in this result, so here is the
>>letter :)
>>PS If somebody could ask Xalan guys to get rid of new PrintWriter() -
>>this would be great :)
>>
>
> Did post a message on Xalan Dev?
Please do!
>>PPS XSPs *are* fast. XSL is slow :-|
>>
>
> ...but people say XSPs are not skaling very good. AFAIR (vaguely) Berin
> tracked this down (also with optimizeIt) and it was a classloader issue.
> Berin, is this right? Please correct me if I am wrong... I guess this
> raised the monitoring thread...
>
> (Sorry didn't find the correct message in the archives)
It wasn't me who used OptimizeIt, I think it was Sylvain. There are a number
of issues with XSP, though. Here are a few:
1) Classloader issues. sometimes the XSP system won't let go of the reference
to the old class, causing the new XSP to be recompiled every time and never
used. This was fixed when we moved the generated XSP from the root of the
work directory.
2) The wrapping the calls of the XSP to handle "return" calls in the middle of
a SAX stream. I think we decided to remove this "feature", but I don't recall
if it was actually done.
3) Evaluation on whether the XSP is current takes a long time, and incurs
accessing the filesystem with each request. Making the compiled elements'
management asynchronous will help in this area.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
