- From: Reed Wade <wade@cs.utk.edu>
- Date: Wed, 15 Feb 1995 16:05:13 -0500
- To: ietf-lists@proper.com (Paul Hoffman)
- Cc: Reed Wade <wade@cs.utk.edu>, uri@bunyip.com
>Reed, these are clearly client implementation issues. Anyone writing a >URL-reading finger client would have to look at how she/he would want to >parse and send. I believe this is probably beyond what belongs in a URL >description; look at how little client stuff appeared in RFC 1738. At minimum, tho, you _must_ unambiguously indicate what part is data and what part is connection info. That's what the //host:port/ muck in 1738 is for. If that type of host info is not used in the url (as we're suggesting) then there needs to be some other way of indicating what's what. There are 2 potential interpretations of what might go out on the wire. This ought to be resolved and not left to implementational caprice. -reed ----- University of Tennessee, Knoxville Dept of Computer Science Netlib Development Group 'I was kidding,' says bomb suspect wade@cs.utk.edu -- <URL:http://www.netlib.org/utk/people/ReedWade.html>
Received on Wednesday, 15 February 1995 16:05:01 UTC