Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 2435 invoked by uid 500); 2 Oct 2000 22:07:00 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 2408 invoked from network); 2 Oct 2000 22:06:57 -0000 Message-ID: From: "Fielding, Roy" To: "'new-httpd@apache.org'" Subject: RE: cvs commit: apache-2.0/src/main http_core.c http_protocol.c Date: Mon, 2 Oct 2000 15:06:51 -0700 X-Mailer: Internet Mail Service (5.5.2650.21) X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I don't see what the big deal is about a buffer filter. Coalescing is necessary if the data that is about to be sent out the network is less than a defined (configurable) threshold and the stream is not in a non-buffering mode. That coalescing can take place either within the TCP_CORK (if we are lucky to have one) or a buffering layer. Assuming that the module will implement writes "efficiently" is not a reasonable thing for the server to do. This is not a question of design purity -- I was always assuming that such a layer would exist, for the same reason that BUFF exists. ....Roy