From owner-freebsd-hackers Mon Mar 2 05:21:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11933 for freebsd-hackers-outgoing; Mon, 2 Mar 1998 05:21:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) 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 FAA11921 for ; Mon, 2 Mar 1998 05:21:23 -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 FAA22936; Mon, 2 Mar 1998 05:22:28 -0800 Date: Mon, 2 Mar 1998 05:22:27 -0800 (PST) From: Alex Belits To: Amancio Hasty cc: Niall Smart , hackers@FreeBSD.ORG Subject: Re: A web-based FreeBSD configuration tool. In-Reply-To: <199803021307.FAA10631@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Mar 1998, Amancio Hasty wrote: > Well, all this is academic for "we ain't got no" application developers > in this group . Actually I'm trying to do something with the lists handling and transactions through HTTP, and I hope, either me or someone else will write an interface/framework that will allow route/replicate/process HTTP-based transactions over the network to implement "mass-update" and monitoring for the network (NIS-backward or SNMP-like administration protocol over HTTP). Nothing to speak of yet, except mentioned by me multiple times before my HTTP server with its API, suitable for transactions mechanism. -- Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message