From owner-freebsd-current Mon Jan 5 07:10:01 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA09720 for current-outgoing; Mon, 5 Jan 1998 07:10:01 -0800 (PST) (envelope-from owner-freebsd-current) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA09690 for ; Mon, 5 Jan 1998 07:09:54 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.5) id KAA23284; Mon, 5 Jan 1998 10:09:42 -0500 (EST) Date: Mon, 5 Jan 1998 10:09:42 -0500 (EST) From: Garrett Wollman Message-Id: <199801051509.KAA23284@khavrinen.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Time to retire fetch? In-Reply-To: <4721.883994636@time.cdrom.com> References: <4721.883994636@time.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > I just noticed that FTP in -current now supports http:// style > fetches, a feature which seems to have crept in under my nose during > the sync with NetBSD's ftp client. And I made it know at the time my strong opposition to such changes. It's simply idiotic for an interactive for the FTP protocol to know the slightest thing about the HTTP protocol. (Another bogus change at the same time: the `ls' command was broken to generate the `NLST' command instead of `LIST'.) AFAIK, fetch is still the only client we have to do MD5 digests, HTTP authentication, HTTP/1.1, transaction TCP, and transparent redirects. The ports collection may not require these things, but the ports collection is not the whole universe. Granted, I have some auctorial interest in this particular implementation. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick