Return-Path: Delivered-To: apmail-httpd-test-dev-archive@httpd.apache.org Received: (qmail 55170 invoked by uid 500); 19 Feb 2003 01:20:47 -0000 Mailing-List: contact test-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: test-dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list test-dev@httpd.apache.org Received: (qmail 55153 invoked from network); 19 Feb 2003 01:20:46 -0000 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Tue, 18 Feb 2003 17:20:48 -0800 Subject: Re: SPEC / mod_specweb99.c From: Sander Temme To: "test dev httpd.apache.org" Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Does anybody know if the mod_specweb99.c been 'blessed' by the SPEC > committee ?..I mean, have they acknowledged that the module acts in a SPEC > compliant manner? As far as I am aware, the module has not been used for benchmarks submitted to the SPEC organization. That is the moment any code would get 'blessed': SPEC validates the results and the way they were obtained and the benchmarkee submits the API source code as part of this process. > I had a doubt regarding executing CGI scripts in SPECweb99 - somebody here > told me that the SPEC mandates the web server to fork a child process to > execute a CGI script - is that so ?. This is the case for Dynamic CGI GET requests. You set a special URL for this in your rc file. All other dynamic requests can be processed by in-process code and most if not all submittors have written code for this. S. -- Covalent Technologies sctemme@covalent.net Engineering group Voice: (415) 856 4214 303 Second Street #375 South Fax: (415) 856 4210 San Francisco CA 94107 PGP Fingerprint: 7A8D B189 E871 80CB 9521 9320 C11E 7B47 964F 31D9