Re: New Internet-Draft: finger URL

>The important question is whether I loose any functionality. Imagine
>these 2 situations:
>1. I type at my command line "finger"; the
>   finger command on my machine opens a tcp connection to the finger
>   server at and sends "wade".
>2. With finger:<> how can I send a "wade" to
>   the finger server at honk?
>   The finger server on honk may or may not treat the 2 requests
>   ("wade", "") differently. We can't assume
>   they would do one thing or the other.

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.

Received on Wednesday, 15 February 1995 14:58:01 UTC