Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 50151 invoked from network); 14 Apr 2002 21:37:05 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 14 Apr 2002 21:37:05 -0000 Received: (qmail 21043 invoked by uid 97); 14 Apr 2002 21:37:07 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 21027 invoked by uid 97); 14 Apr 2002 21:37:06 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 21016 invoked from network); 14 Apr 2002 21:37:06 -0000 Message-ID: <004e01c1e3fc$8e691680$80080b50@apache.org> From: "Remy Maucherat" To: "Tomcat Developers List" References: <20020414103031.17015.c007-h005.c007.wm@mail.distributopia.com.criticalpath.net> Subject: Re: Corrupted Ouput - Tomcat 4.0.3 Date: Sun, 14 Apr 2002 14:37:18 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Remy Maucherat wrote: > > > > > There seems to be a bug in the servlet output. > > > > Tomcat 4 does not corrupt images, binaries, or anything like that. This has > > been proven on and on by many people using it (like myself) on various > > websites. > > > > That logic doesn't work. The fact that it works for > some people, even the vast majority of people, is no > proof at all that it works for everyone. Although I cannot mathematically prove it, there is not in the Tomcat codebase (o.a.catalina.* packages) any incorrect handling of binary output which would cause binary corruption. So I stand by my statement. I don't see any need for doubt when there should not be any. After that, the network stack of the VM is a black box, so anything can happen (for example, the connector is using TCP no delay set to true; maybe that could be causing problems). Remy -- To unsubscribe, e-mail: For additional commands, e-mail: