Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Date: Fri, 25 Aug 2000 11:20:30 -0700
From: Alex Chaffee <guru@edamame.stinky.com>
To: tomcat-dev@jakarta.apache.org
Subject: Re: BUG: flushBuffer in Jasper
Message-ID: <20000825112030.P14336@edamame.stinky.com>
Reply-To: alex@jguru.com
References: <20000825084608.B14336@edamame.stinky.com>
 <39A6FF1D.64DB792E@yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <39A6FF1D.64DB792E@yahoo.com>;
 from cmanolache@yahoo.com on Fri, Aug 25, 2000 at 04:19:57PM -0700

On Fri, Aug 25, 2000 at 04:19:57PM -0700, cmanolache@yahoo.com wrote:
> I'm not sure I understand the problem.
> Jasper should flush it's own buffers before calling any flush downstream.

It does.  But flushBuffer is a method on *response*, which was passed
in from Tomcat, which has its own buffer.  Which it flushes.  But
Jasper's buffer is somewhere else (inside JspWriterImpl), that
Response doesn't know about, so it stays full.

There's a JspWriter whose flush method works fine.  But there's no
"JspResponse" or equivalent (that would be my facade solution).

This is really the fault of the API; I see no reason for having a
Response.flushBuffer() call when out.flush() should (and does) do the
job perfectly well.  Maybe I should ask the JSR 53 experts why they
added this method to Response.

-- 
Alex Chaffee                       mailto:alex@jguru.com
jGuru - Java News and FAQs         http://www.jguru.com/alex/
Creator of Gamelan                 http://www.gamelan.com/
Founder of Purple Technology       http://www.purpletech.com/
Curator of Stinky Art Collective   http://www.stinky.com/