Re: A few questions.....

Tom Leete (tleete@access.mountain.net)
Thu, 24 Jun 1999 20:37:57 -0400

-----Original Message-----
From: jerome@psti.com <jerome@psti.com>
>ex: i have a program and his command line requires a list of file
>and i want one of them as "http://.." or "/http/.." (choose the one
>you prefer). a pipe cant satify this case.
>
>for PUT, write() seems ok.
>for POST,... i dunno :) what is the purpose of the POST command ?
>
>On Thu, Jun 24, 1999 at 05:39:26PM +0100, Jan-Simon Pendry wrote:
>>
>> use the perl GET command ...
>>
>> GET http://www.site.org/index.html | less
>>
>> or use a shell (which is there for a reason)
>>
>> diff <(GET http://sometime.org) <(GET http://sometime.com)
>>
>> a large problem with hiding this functionality inside open() is
>> that the URL is not the only attribute being sent in the HTTP/1.1

I think this points out the real problem with this idea.

The protocol identifiers http:// , news://, etc. may look like fs roots, but
that's just the notation. They are really shells.

If you have the URI: http://foo.bar/baz/index.html and assume your shell
groks DNS & portnames that might translate to the *nixic:
foo.bar:http /baz/index.html

My point is that a network shell is different from a network file system, or
at least it ought to be. open() and family is for files.

Regards,
Tom

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/