> -----Original Message----- > From: Torsten Curdt [mailto:[EMAIL PROTECTED]] > Sent: maandag 28 januari 2002 15:25 > To: [EMAIL PROTECTED] > Subject: Re: Who needs 386% speed up? > > <snip> > > > 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*
Everybody talks about returns, but what about exceptions. Should we also document that possible exceptions in an XSP page are considered *bad*? Or am I missing the point here? Michael > > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
