Received: by taz.hyperreal.com (8.6.12/8.6.5) id QAA06624; Wed, 6 Dec 1995 16:18:49 -0800 Received: from aldhfn.aldhfn.org by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id QAA06612; Wed, 6 Dec 1995 16:18:45 -0800 Received: from main.slink.com (slink.com [199.18.242.17]) by aldhfn.aldhfn.org (8.6.12/8.6.11.1) with SMTP id TAA08825 for ; Wed, 6 Dec 1995 19:18:39 -0500 Received: from garey.slink.com by main.slink.com (IBM OS/2 SENDMAIL VERSION 1.3.15/(1.0sosum) for new-httpd@hyperreal.com; id AA9462; Wed, 06 Dec 95 19:27:20 -0500 Message-Id: <9512070027.AA9462@main.slink.com> Date: Wed, 06 Dec 95 19:27:07 EST From: garey@main.slink.com (Garey Smiley) To: new-httpd@hyperreal.com X-Mailer: PMMail v1.1 UNREGISTERED SHAREWARE Subject: Re: New feature: TGI? Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Wed, 6 Dec 1995 15:53:38 -0800 (PST) you wrote: > I don't think this answers the question. What makes this >different from the API. Not what makes this different from CGI. Lokos >like verything you describe below can be done with the existing >API. (Not that I don't think we need the added functionality of a >protocol API, that is seperate.) When you say "API" are you refering to the Apache module API? If so, TGI is just another module that adds a type of CGI. For more details on exactly what TGI does and how it works refer to http://bws.roma.ccr.it/httpd2doc/tgi_en.html. Garey Smiley SoftLink Services garey@slink.com http://www.slink.com/ (216)848-1312 FAX/Data(216)699-4474