Randy Belknap wrote:
> This is a general servlet api design question. The way servlets (and
> ASP) are designed, the only url's that are rewritten are the ones that
> you explicitly wrap in the encode method. Was there ever a discussion
> about being able to parse all servlet output looking for urls and
> rewriting them?
>
It's certainly feasible for a servlet container to offer this feature -- no API
change is required. Don't forget to do this only for "text/html" responses, though
-- you don't want things like dynamically generated images, or serialized Java
object streams being sent back to an applet, to get mangled.
For my apps, I would still choose not to pay the performance price of this extra
scan. When I write my servlet or JSP page, I know where the hyperlinks are
already, and can encode them suitably. I want my servlet container to send the
bytes of my response back to the client as fast as it possibly can.
Craig McClanahan
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
