--On Friday, August 31, 2001 09:58:21 -0700 Richard Hodges
<[EMAIL PROTECTED]> wrote:
> On Fri, 31 Aug 2001, Paul Richards wrote:
>
>> A URI is a Universial Resource Indicator, it's not a web browser address.
>>
>> On the other hand, what exactly is http://www.ufp.org supposed to be
>> useful for when www.ufp.org is the same thing.
>
> Why not parse it literally? For instance, http://www.ufp.org
> would imply TCP, dest port 80, and host www.ufp.org.
I think that's a reasonable idea. A library that parsed URI's and returned
a struct with the broken out information would be a reasonably useful tool.
> On second thought, it looks like most Internet apps would have to
> be rewritten to understand this new functionality.
What apps did with the information from the URI is probably up to them.
>> What would happen if I did mutt http://www.ufp.org ?
>
> In this case, mutt should do an HTTP request to port 80 at www.ufp.org,
> grab the home page, and put it in your inbox :-)
If that's what the mutt developers wanted to do with the URI then why not?
Having a set of URI functions might be useful. How many applications get
changed to make use of the functionality and in what ways is probably
something different to think about and something that can be done on an
application by application basis (with an overall aim for consistency
though).
Paul Richards
FreeBSD Services Ltd
http://www.freebsd-services.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
