- From: Michael A. Dolan <miked@ncd.com>
- Date: Tue, 14 Feb 1995 17:21:27 -0800
- To: ietf-lists@proper.com (Paul Hoffman), uri@bunyip.com
At 02:34 PM 2/14/95 -0700, Paul Hoffman wrote:
>IETF URI Working Group
>Internet-Draft
>draft-ietf-uri-url-finger-00.txt
>Expires August 15, 1995
>
> finger URL Specification
>
> finger:<request>
Doesn't this presume a local fingerd and/or a hard-wired fingerd host/port ?
I kinda liked Reed's last draft.......
>Date: Wed, 24 Aug 1994 04:56:14 +0200
>From: Reed Wade <wade@cs.utk.edu>
>To: Multiple recipients of list <www-talk@www0.cern.ch>
>Subject: Finger URL, second cut
>
>After looking over the finger rfc again and assimilating
>comments I've made some changes to my original finger URL
>proposal.
>
>
>Reed Wade
>---------
>wade@cs.utk.edu -- http://www.netlib.org/utk/people/ReedWade.html
>
>
>
>Finger URL
>
>
>
>finger://hostname/[W/][username][hostlist]
>
>hostlist ::= @hostname | @hostname{hostlist}
>
>
> finger://cs.utk.edu/@garlic
> finger://cs.utk.edu/W/wade@honk@garlic
> finger://cs.utk.edu/W/ <-- these are different,
> finger://cs.utk.edu/W <-- here W is the username
> finger://cs.utk.edu/wade
>
>Encoded CR's and LF's are not permitted in any part of the URL.
>
>If the "W/" element is present then the finger request is preceded
>by the /W (or /W<sp> as required) per rfc1128.
>
>
>
>Returned Data Interpretation:
>
>Existing finger servers return user information in unpredictable
>ways. There are cases where it is not possible to get information
>on only a single user. Interpreting returned data as plain text
>is the only reasonable thing to do. Instead of attempting to wedge
>more utility into finger, whois++ or http should be used.
>
>
>
>
-----------------------------------------------
Michael A. Dolan <mailto:miked@ncd.com>
Vice President, Strategic Planning
Network Computing Devices, Inc. (619) 445-9070
FAX -8864
Received on Tuesday, 14 February 1995 20:24:37 UTC