From owner-freebsd-hackers Thu May 11 22:44:46 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA03985 for hackers-outgoing; Thu, 11 May 1995 22:44:46 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA03937 for ; Thu, 11 May 1995 22:44:24 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id NAA00312; Fri, 12 May 1995 13:43:03 +0800 Date: Fri, 12 May 1995 13:43:02 +0800 (CST) From: Brian Tao To: Terry Lambert cc: freebsd-hackers@FreeBSD.org Subject: Re: Apache + FreeBSD 2.0 benchmark results (fwd) In-Reply-To: <9505111732.AA00778@cs.weber.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Thu, 11 May 1995, Terry Lambert wrote: > > It's clear, but it's redundant. All forking is "demand forking", in > that a fork will not occur unless you "demand" it by calling "fork". I suppose it depends on your point-of-view. Traditional httpd's will fork when a client demands a connection. NCSA httpd 1.4 in "forkless" mode does not. It does all the forking and execing at the beginning (on demand from the master httpd, but not from the HTTP client) and, in most cases, does not fork when a client wants a connection. I suppose I'll stick with it just to make a clear distinction between the two. > My car has "demand start". 8-). Ah, but not all do. I used to own a car that didn't have demand starting, especially on a cold Canadian winter morning. ;-) > > Perhaps a new httpd could be modelled on IRC. *shudder* :) > > Please, no! The model is not that effecient in the first place, and > the IRC server is as bad a code example as most muds in the second! Okay, okay... just kidding. ;-) > That's the wonderful thing about CS terms -- there are so many to choose > from. What you have is an I/O Dispatching server according to what I've > been taught . A term I've heard running around the httpd circles is a "salad shooter" server. Apparently there is a product of American marketing genius that consists of a handheld piece of kitchen equipment shaped and held like a gun. One drops various salad ingredients into one end of the implement, some sort of mechanical processing takes place inside the contraption, and out the business end of the gun comes a "stream of salad". You aim this thing at a lunch patron's bowl, and fire. Amazing. I've not seen this ad (sounds like something that would come on after the late, late night movie), but I'm told it can shoot several streams of salad at once, analagous to a single information server process that can handle multiple data streams. Am I making any sense? ;-) -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org