Re: [9fans] gtk port

[Randolph Fritz <randolph@cyber-dyne.com>]

On Fri, Jun 30, 2000 at 01:55:06AM +0000, James A. Robinson wrote:
>
> I was thinking of acme's model where each window get's it's own id and
> file system.  So each host would have it's own hierarchy. My example
> was poor, I should have posted something along the lines of:
>
>   /mnt/web/new/ctl      (open a new <id> proto://host:port)
>   /mnt/web/new/get      (get back an <id> with data filled from GET)
>
>   /mnt/web/id/get       (quick 'n' dirty GET request)
>   /mnt/web/id/set       (set ?default? outgoing headers/httpauth)
>   /mnt/web/id/post      (longer data submissions?)
>   /mnt/web/id/headers/* (incoming header response)
>   /mnt/web/id/body      (read the body of the response)
>
> Or somesuch. With a private namespace for each host, you don't
> worry about long filenames.
>

Having thought it over, I think you're right.  As Skip T points out:
>
> It would be nice to follow the example of ftpfs, but http
> does not map to a filesystem nicely. I suspect that is why there is
> an hget in the distribution and not an httpfs. For example what should
> the content of /http/x.y.com/i.html be, if a GET of 'http://x.y.com/i.html'
> results in a redirect? How does one represent a query parameter of a URI
> in a filesystem (like http://x.y.com/i.html?user="sam")? etc.
>

The following might be addressed by an NGLayout port:
>
> It seems that the display problems would be straight forward with LOTS
> of code to display HTML (?and interpret Javascript?) and a little
> code for a go-between filter to acme.
>

On Thu, Jun 29, 2000 at 08:41:31PM -0500, Jim Choate wrote:
> I must disagree here, for example:
>
> .../httpd/einstein.ssz.com/index.html
>                           /cdr
>                           /cdr/index.html
>                           /cliology
>                           /cliology/index.html
>                           /...
>          /google.com
>

But many sites aren't organized that way. :( The web's metadata format
is more confused than FTP's.  Hmmm...I don't really understand W3's
RDF metadata format, but that might offer a key to the problem.

--
Randolph Fritz
Eugene, Oregon, USA