From owner-freebsd-config Sun Feb 1 22:46:05 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12443 for config-outgoing; Sun, 1 Feb 1998 22:46:05 -0800 (PST) (envelope-from owner-config) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12438 for ; Sun, 1 Feb 1998 22:46:04 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id XAA12150; Sun, 1 Feb 1998 23:45:57 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd012087; Sun Feb 1 23:45:50 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id XAA15364; Sun, 1 Feb 1998 23:45:43 -0700 (MST) From: Terry Lambert Message-Id: <199802020645.XAA15364@usr01.primenet.com> Subject: Re: WebAdmin To: abelits@phobos.illtel.denver.co.us (Alex Belits) Date: Mon, 2 Feb 1998 06:45:43 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, rivers@dignus.com, capriotti0@hotmail.com, capriotti@geocities.com, config@FreeBSD.ORG, joe.shevland@horizonti.com In-Reply-To: from "Alex Belits" at Feb 1, 98 09:51:08 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-config@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > HTTP has implicit transaction identifier as the representation of > request and response to it are tied together at both client and server > even though there is no explicit identifier that server and client share. > This identifier is replaced by the protocol state in the protocol and > exists on client as paired request and received response to it and at the > server as the same thing (sometimes in rather primitive form of CGI > process id, sometimes as TCP connection, if persistent connections aren't > used, sometimes explicitly). This is not terrifically useful for a text-only install on a serial console. Remember that whatever technology is selected must work without http. What you are describing is an implementation detail for a general interface. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.