From: Randy Terbush <randy@zyzzyva.com>
Message-Id: <199512071620.KAA05012@sierra.zyzzyva.com>
Subject: Re: New feature: TGI?
To: new-httpd@hyperreal.com
Date: Thu, 7 Dec 1995 10:20:15 -0600 (CST)
In-Reply-To: <199512071547.HAA14857@eitech.eit.com> from "Geoff White" at Dec
 7, 95 07:47:10 am
Content-Type: text
Content-Length: 977       
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

> 
> At 09:16 PM 12/6/95 -0600, new-httpd@hyperreal.com wrote:
> >> 
> >> Benefits as I see then: (this is open to interpertaion ;-)
> >> 	- Speed.
> >> 	- Allows for complex applications.
> >> 	- Any where you can put a URL (href, img, get, post, etc.) 
> >> 	  a TGI deamon can be called to do something.
> >> 	- TGI  deamons can be started and stoped as needed
> >> 	  without stoping the server.
> >> 	- Rights to access TGI URLs are still controlled by the 
> >> 	  server's standard access control (access.conf, .htaccess, etc.).
> >> 
> >
> >These features are all available in the module API that Robert Thau
> >provided us in Apache. 
> 
> Um not quite, from what I understand this also allows you to create
> portable modules, if I implement TGI for Netsite [ack!] then the modules
> would be interchangeable between servers compiled for the same OS/CPU
> architecture?

If you implement the Apache API on Netsite you could also do this
with the Apache modules, no?