9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "John E. Barham" <jbarham@jbarham.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] WebDAV file system
Date: Wed, 30 Oct 2002 11:13:20 -0800	[thread overview]
Message-ID: <015d01c28048$696e6b80$620da8c0@HPN5415> (raw)
In-Reply-To: <e37d02a183b422d3963023618770a396@collyer.net>

Geoff Collyer wrote:

> > the way yet another thing gets hacked in on top of another hack and
> > so on ...
>
> I thought FTP was an overly-complex botch of a protocol, but when I
> was told what WebDAV was (HTTP as [lousy] remote file system
> protocol), I felt sick to my stomach.  Apple claim that they developed
> this abomination, but they could have just used IMAP, which clearly
> already is a [rotten] remote file system protocol but doesn't know it.

Give WebDAV some credit...  It does have several nice benefits over FTP:
easier custom authentication (assuming you're using something like Apache),
encryption via SSL, HTTP caching.  Being able to attach artitrary properties
to WebDAV resources also opens up some interesting possibilities:  for
example, I'm writing a unified POP3/IMAP/Webmail system that uses WebDAV as
the mail repository which means I can pre-parse the message headers and
store them as properties, somewhat reminiscent of how the Plan 9 mail file
server works.  It also makes remote, cross-platform development of the
servers trivial and I can browse the mail repository in my web browser.

> HTTP was a hack to transport the much worse hack of HTML and now
> they're piling kludges on top of hacks.

So the web is a hack.  Maybe several hundred million people can be wrong,
;), but it's easier (technically and politically) to make Plan 9 interop w/
what's out there in wide use than vice versa.

> (Is there really any point to
> using XML?  Maybe I'm missing the obvious, but I don't see that it
> buys one anything.)

It does seem gratuitous to use XML for WebDAV properties.

> How many awful, truncated remote file system protocols are people
> going to invent before they just bite the bullet and use a real one?

How many journaling file-systems does Linux really need?  People will insist
on re-inventing wheels (maybe badly) but for whatever reasons some of them
do pick up momentum and I might as well go along for the ride.

    John



  parent reply	other threads:[~2002-10-30 19:13 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 10:45 Geoff Collyer
2002-10-30 13:17 ` rob pike
2002-10-30 13:27   ` Lucio De Re
2002-10-30 18:11     ` Jim Choate
2002-10-30 14:40 ` Ronald G Minnich
2002-10-30 19:13 ` John E. Barham [this message]
2002-10-30 20:34   ` Dan Cross
  -- strict thread matches above, loose matches on Subject: below --
2002-11-04 18:49 Charles Forsyth
2002-11-04 15:15 Skip Tavakkolian
2002-10-31 14:38 Skip Tavakkolian
2002-11-04 18:38 ` Peter Downs
2002-11-05 18:47   ` Dan Cross
2002-10-31  5:26 okamoto
2002-10-31  5:15 okamoto
2002-10-31  6:35 ` Jim Choate
2002-10-31  4:17 Skip Tavakkolian
2002-10-31 13:58 ` Jim Choate
2002-10-31 18:21   ` Dan Cross
2002-11-01 11:26     ` Boyd Roberts
2002-11-01 20:50       ` Dan Cross
2002-11-01 23:30   ` Roman V. Shaposhnick
2002-10-31  2:59 okamoto
2002-10-31  5:18 ` Jim Choate
2002-10-30 18:21 rob pike, esq.
2002-10-30 22:00 ` Jim Choate
2002-10-30 17:21 Russ Cox
2002-10-30 21:55 ` Jim Choate
2002-10-30 15:42 Skip Tavakkolian
2002-10-30  9:37 C H Forsyth
2002-10-30  8:55 okamoto
2002-10-30  8:31 Charles Forsyth
2002-10-30 13:14 ` rob pike
2002-10-30 14:16 ` Jim Choate
2002-10-30  6:29 Russ Cox
2002-10-30 11:06 ` Boyd Roberts
2002-10-30  4:10 Skip Tavakkolian
2002-10-30  3:12 John E. Barham
2002-10-30  5:53 ` Jim Choate
2002-10-30  6:14   ` John E. Barham
2002-10-30 14:13     ` Jim Choate

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='015d01c28048$696e6b80$620da8c0@HPN5415' \
    --to=jbarham@jbarham.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).