On Monday, October 6, 2003, at 03:23 PM, Nathan Bubna wrote:
Geir Magnusson Jr. said:On Monday, October 6, 2003, at 01:37 AM, Nathan Bubna wrote:...here's what i'm leaning toward for the VVS (no opinion yet as to whether VelocityServlet should do the same):
1. take Matthew's suggestion and use response.getWriter() instead of getOutputStream(). (also use getWriter() in the error() method.)
I think we should do this in VelocityServlet for consistency. I'd like
to see VS go and point people towards VVS, but for backwards compat, we
should keep it around.
ok.
Is there a simple, basic example of using VVS?
so, for those wanting to set the charset (character encoding)
per-application,
they then need only set it as part of their content-type in their
velocity.properties. (i suppose we could also still accept an encoding
separately in velocity.props and concat it to the content-type during
servlet
init)
Won't that be confusing?
i don't think so. as it is, they can already specify charset as part of their
default.contentType in their velocity.properties. after all, it's the way the
servlet API is set up; there's no setCharset() method for ServletResponse.
also, if we take my parenthesized suggestion, then that should provide them a
way to specify content-type and charset separately. would that be
non-confusing enough?
I think so. I'll have to take a look again at VS. It's been a while, but I remember it was confusing for some poeple - I'm just thinking that if you have a better, cleaner way, we should use that.
-- Geir Magnusson Jr 203-247-1713(m) [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
