Message-Id: <firstname.lastname@example.org> Date: Wed, 15 Feb 1995 11:58:13 -0700 To: Reed Wade <email@example.com> From: firstname.lastname@example.org (Paul Hoffman) Subject: Re: New Internet-Draft: finger URL Cc: email@example.com >The important question is whether I loose any functionality. Imagine >these 2 situations: > >1. I type at my command line "finger firstname.lastname@example.org"; the > finger command on my machine opens a tcp connection to the finger > server at honk.cs.utk.edu and sends "wade". > >2. With finger:<email@example.com> 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", "firstname.lastname@example.org") 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.