From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1BkuKB-0006kG-36
	for qemu-devel@nongnu.org; Wed, 14 Jul 2004 20:42:11 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1BkuK5-0006iX-7q
	for qemu-devel@nongnu.org; Wed, 14 Jul 2004 20:42:10 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1BkuK5-0006iU-4Q
	for qemu-devel@nongnu.org; Wed, 14 Jul 2004 20:42:05 -0400
Received: from [203.63.55.34] (helo=wallace.eclinic.com.au)
	by monty-python.gnu.org with smtp (Exim 4.34) id 1BkuH6-0000vi-TB
	for qemu-devel@nongnu.org; Wed, 14 Jul 2004 20:39:01 -0400
Subject: Re: [Qemu-devel] Win98: how to exchange data with Linux
From: Leigh Dyer <leigh@eclinic.com.au>
In-Reply-To: <1089823480.1160.124.camel@aragorn>
References: <1089671145.12301.10.camel@aragorn>
	<200407130924.58879.vaise@votreservice.com>
	<1089727701.7843.58.camel@espiron.av7.local>	<40F3EF20.2020802@kadu.net>
	<40F3F5B1.2040908@kadu.net>	<40F41A65.8050807@volny.cz>
	<1089740739.17526.3.camel@aragorn>	<40F422BB.8020908@kadu.net>
	<1089742289.13010.20.camel@aragorn>	<40F42A9D.5000901@kadu.net>
	<20040714024203.GD6436@jbrown.mylinuxbox.org>
	<40F501E8.7030405@kadu.net>
	<40F514D1.1010008@bellard.org>  <1089823480.1160.124.camel@aragorn>
Content-Type: text/plain
Date: Thu, 15 Jul 2004 10:38:29 +1000
Message-Id: <1089851909.19121.28.camel@shawn.local>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Wed, 2004-07-14 at 09:44 -0700, John R. Hogerhuis wrote:
> On Wed, 2004-07-14 at 04:11, Fabrice Bellard wrote:
> 
> > 1) built-in FTP server in the SLIRP layer.
> 
> HTTP was intended at least in part to replace FTP. It might make more
> sense as a file transfer protocol. Maybe integrate a simple web server
> into SLIRP layer instead of FTP?

I also like the idea of a web server instead of an FTP server. A basic
web server would be quite a bit easier to write than an FTP server, and
it could later be extended with a basic WebDAV implementation to support
more filesystem-like read-write access.

The downside is that WebDAV is possibly more complex to implement than
FTP, and a HTTP server without WebDAV is only really a partial solution,
since there's no really easy way to do guest->host transfers.

Thanks
Leigh