From owner-freebsd-config Sun Feb 1 21:36:02 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06301 for config-outgoing; Sun, 1 Feb 1998 21:36:02 -0800 (PST) (envelope-from owner-config) Received: from phobos.illtel.denver.co.us (abelits@phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06280 for ; Sun, 1 Feb 1998 21:35:57 -0800 (PST) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.8/8.6.9) with SMTP id VAA20275; Sun, 1 Feb 1998 21:51:09 -0800 Date: Sun, 1 Feb 1998 21:51:08 -0800 (PST) From: Alex Belits To: Terry Lambert cc: Mike Smith , rivers@dignus.com, capriotti0@hotmail.com, capriotti@geocities.com, config@FreeBSD.ORG, joe.shevland@horizonti.com Subject: Re: WebAdmin In-Reply-To: <199802020243.TAA04766@usr01.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-config@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 2 Feb 1998, Terry Lambert wrote: > > You fail to understand. The entire point that you have missed is that > > the 'transaction' that Terry is talking about is a transition whereby a > > set of separate parameters assume new values in an atomic fashion. > > This is exactly what I mean. > 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). -- Alex