Michael Homeijer wrote:
>>-----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?
No, you have the point. An exception signals that something is wrong.
There is the ResourceNotFoundException which signifies that processing
cannot continue because the source file is not there. Generally speaking,
any exception thrown from the pipeline generates an error page. Therefore,
everyone is pretty confident that throwing exceptions on purpose is not
good.
--
"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]
