From owner-freebsd-hackers  Mon Nov 27 16:36:16 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id QAA15006
          for hackers-outgoing; Mon, 27 Nov 1995 16:36:16 -0800
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA14996
          for <hackers@freebsd.org>; Mon, 27 Nov 1995 16:36:13 -0800
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id QAA00855; Mon, 27 Nov 1995 16:34:41 -0800
To: Bakul Shah <bakul@netcom.com>
cc: hackers@freebsd.org
Subject: Re: Thoughts on the install and on Red Hat Linux. 
In-reply-to: Your message of "Mon, 27 Nov 1995 11:37:18 PST."
             <199511271937.LAA05263@netcom22.netcom.com> 
Date: Mon, 27 Nov 1995 16:34:41 -0800
Message-ID: <853.817518881@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
Precedence: bulk

> put in links for help files etc.  I really should put
> together a prototype.... anyway, if anyone is interested we
> can explore this idea further.

I'd like to see the prototype.. :-)

Believe me, this idea has crossed my mind more than once.  In another
mailing list, I was talking with some folks for awhile about the idea of
implementing "http server" capability for existing applications.

Instead of going for a full httpd and CGI interface, you implement a
library that allows pretty much any event driven application to "grow
an HTTP port".  You write your "forms" in a higher level pastiche of
HTML and some sort of imbeded tags that let you specify which callback
routines to call when a given HTML object is manipulated in some way.

The viewer would see HTML, your legacy app would see a different sort
of command interpreter.

Would you be interested in exploring an option like that, as well as
the option of using existing server technology and CGI?

					Jordan