Geir Magnusson Jr. wrote: > On 7/30/02 8:44 AM, "Rickard" <[EMAIL PROTECTED]> wrote: > Because we miss you and wanted you to come back.
I KNEW it!! :-) > 1) Worries me as you can forget to put back. However, one might argue that > you take our chances when doing this.... Add "get/return" methods that wrap 'em, add Javadocs "Don't forget to return the writer or die", and spank those who come to the dev list saying "my writers aren't pooooled, what's wrong?" and generally ignore it as it's not exactly *that* worrisome to forget to put it into the pool. It just works worse. > 2) Only worries is that not-Rickard will come and say "Hey, you are using > writer an I need the output stream later..", but as we never made any > promises re this, it may be ok. :-) That'd be great. I'm currently working on implementing the Portlet API (JSR168) and portlets are supposed to use getWriter() in order to write. Some of my portlets use Velocity (of course), which breaks everything since ya can't use getOutputStream() and getWriter() at the same time. > Thinking about it, if we can keep the writer pool protected, we might as > well do that, so lets go with #2. That'd be muchos appreciated. /Rickard -- Rickard �berg Senselogic -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
