> >>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!

Can anyone subscribed to XalanDev do this - otherwise I will go an
get me subscribed....

> >>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:

As I said - I vaguely remembered ;)

> 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.

ok

> 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.

Hm.. I guess all we decided was to add a comment to the documentation that
return calls in a XSP page are to be considered *bad*

> 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.

What about a config option to turn off this checking ?
For developing checking is mandatory but for a life site that does
not change very often this might give us some more speed.

I wouldn't care to turn it on/off for changes...
--
Torsten


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to