This is not a valid address at SNL Securities (http://www.snl.com).  Please remove 
him/her from your mailing list or address book.


Your message reads:

Received: from snlexch.snl.com (unverified [10.0.1.9]) by mail.snl.com
 (Rockliffe SMTPRA 4.5.4) with ESMTP id <[EMAIL PROTECTED]> for 
<[EMAIL PROTECTED]>;
 Thu, 22 Feb 2001 14:27:50 -0500
Received: by SNLEXCH with Internet Mail Service (5.5.2653.19)
        id <F3WAVJ84>; Thu, 22 Feb 2001 14:25:31 -0500
Received: from mail.snl.com (SNLDMZBDC [10.0.0.7]) by snlexch.snl.com with SMTP 
(Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
        id F3WAVJ8S; Thu, 22 Feb 2001 14:25:29 -0500
Received: from apache.org (unverified [64.208.42.41]) by mail.snl.com
 (Rockliffe SMTPRA 4.5.4) with SMTP id <[EMAIL PROTECTED]> for <[EMAIL PROTECTED]>;
 Thu, 22 Feb 2001 14:27:32 -0500
Received: (qmail 73552 invoked by uid 500); 22 Feb 2001 17:52:59 -0000
Received: (qmail 73334 invoked from network); 22 Feb 2001 17:52:56 -0000
Received: from kyoto.javasoft.com (204.160.241.223)
  by h31.sny.collab.net with SMTP; 22 Feb 2001 17:52:56 -0000
Received: from localhost (localhost [127.0.0.1])
        by kyoto.javasoft.com (8.9.3/8.9.3) with ESMTP id JAA19479;
        Thu, 22 Feb 2001 09:25:33 -0800
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
Reply-To: [EMAIL PROTECTED]
list-help: <mailto:[EMAIL PROTECTED]>
list-unsubscribe: <mailto:[EMAIL PROTECTED]>
list-post: <mailto:[EMAIL PROTECTED]>
Delivered-To: mailing list [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Date: Thu, 22 Feb 2001 09:52:58 -0800 (PST)
X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: TC3.2.1 - response commit on included JSPs
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

On Wed, 21 Feb 2001, Mel Martinez wrote:

> IMHO out.flush() should not commit the response.  Only
> response.flushBuffer() should commit the response. 
> And response.flushBuffer() should not be called from
> an inside an 'include' request.

Hi Mel,

First, JspWriter needs to be flushed at the end of the page - it has a
buffer, and if the buffer is not commited the data will be lost.
There is a method ( flushBuffer ) in JspWriterImpl, and that method should
be called instead of flush().

In 3.2 we had a lot of problems with the buffers - changing that may be a
bit dangerous. For 3.3, the whole buffering has been re-designed and
refactored, and most problems we knew about in the servlet container
are fixed ( but so far this issue hasn't been fixed - to be honest I
didn't knew about it, I've been focused more on the servlet side ).

It shouldn't be difficult to fix it, and since it is a spec issue I think
this is a must_fix bug.

The best way to make sure it'll be indeed fixed is to send a patch or at
least a test case ( a small war with some servlets/jsps and a <gtest>
fragment that we can include in our nighlty tests ). 


Costin






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to