Hi there, Craig wrote:
> Using an include() instead would have other negative consequences -- for > example, you would not be able to set HTTP headers in the error page, due > to the normal restrictions on includes. These are guaranteed to come as a > nasty surprise to users who don't know what underlying mechanism is being > used. Agreed, I didn't see that. The other disadvantages you mentioned are arguable, but this one convinced me. Thanks for this point. Costin wrote: > For JSPs - that's another issue, you could use taglibs ( but that has a > performance impact ) or include the JSPs from a servlet ( another hit, > probably smaller ). I think including from a servlet is a good idea in our case. This should also work reliably in arbitrary containers. Thanks for the suggestion. Best regards --------------------------------------------------------------------------- Dipl.-Inform.(FH) Andreas Junghans Steinbeis-Transferzentrum Industrielle Datenverarbeitung und Automation Moltkestrasse 30 - 76133 Karlsruhe Fon.: +49-721-925-1485 --- Fax: +49-721-925-1488 email: [EMAIL PROTECTED] (privat: [EMAIL PROTECTED]) --------------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
