From owner-freebsd-hackers Sat Sep 1 0:43:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id B8CDF37B405 for ; Sat, 1 Sep 2001 00:43:11 -0700 (PDT) Received: (from fullermd@localhost) by shell.futuresouth.com (8.11.6/8.11.1) id f817glt36569; Sat, 1 Sep 2001 02:42:47 -0500 (CDT) Date: Sat, 1 Sep 2001 02:42:47 -0500 From: "Matthew D. Fuller" To: Richard Hodges Cc: Paul Richards , freebsd-hackers@FreeBSD.ORG Subject: Re: Should URL's be pervasive. Message-ID: <20010901024247.P8939@futuresouth.com> References: <56710000.999257324@lobster.originative.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rh@matriplex.com on Fri, Aug 31, 2001 at 09:58:21AM -0700 X-OS: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oh god, as everybody else is saying, I can't believe I'm getting involved in this, but... On Fri, Aug 31, 2001 at 09:58:21AM -0700, a little birdie told me that Richard Hodges remarked > > Why not parse it literally? For instance, http://www.ufp.org > would imply TCP, dest port 80, and host www.ufp.org. > > For ping, that would imply that I want to test the three-way > handshake on whatever is listening on port 80 at www.ufp.org > > For traceroute, I want to send a series of TCP SYN packets to > www.ufp.org, port 80 with increasing TTL values. Perhaps this No, it doesn't. http://www.ufp.org/ does NOT mean TCP port 80. www.ufp.org:80 means port 80, I don't know of any simple common way to say TCP. http://www.ufp.org/ means the host 'www.ufp.org' using the protocol 'http' with the TCP port 80 implicity as a result of the 'http'. Traceroute is not going to use HTTP. Ping is not going to use HTTP. Rpcinfo is not going to use HTTP. A mail client is not going to use HTTP (this one is perhaps debatable, but I'm sure as hell not going there). If you want to take a URI passed to 'ping', say, and parse out a hostname, that's one thing which I'm sure we could have endless disagreement about. But doing that is *NOT* parsing it as a URI. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message