From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Cc: <hangar18-general@open-forge.org>
Subject: Re: [9fans] WebDAV file system
Date: Tue, 29 Oct 2002 23:53:40 -0600 [thread overview]
Message-ID: <Pine.LNX.4.33.0210292347110.15595-100000@einstein.ssz.com> (raw)
In-Reply-To: <015801c27fc2$2170f8b0$620da8c0@HPN5415>
On Tue, 29 Oct 2002, John E. Barham wrote:
> I'm assuming that given HTTP is a stateless protocol that it would be
> simpler than ftpfs.
The statelessness of HTTP under 9P is not a given since you don't need a
httpd to serve the pages, 9P does that. This means that it is completely
possible to write a state-sensitive browser. The -only- time you need
anything even remotely looking like a httpd under 9P is if you need the
page you want to 'render' to execute one or more programs in a seperate
and secure process namespace that only returns the results (ie server
side equivalent). The advantage to 9P is that it is the client who ends up
paying for that process resource, not the provider.
9P is cool, at least to me, because it does away with the need for the
'server' in a lot of client-server situations. This will eventaully have a
major impact in the way systems are built I suspect. I suspect it will
cause one or more nervous breakdowns as well.
--
____________________________________________________________________
We don't see things as they are, ravage@ssz.com
we see them as we are. www.ssz.com
jchoate@open-forge.org
Anais Nin www.open-forge.org
--------------------------------------------------------------------
next prev parent reply other threads:[~2002-10-30 5:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 3:12 John E. Barham
2002-10-30 5:53 ` Jim Choate [this message]
2002-10-30 6:14 ` John E. Barham
2002-10-30 14:13 ` Jim Choate
2002-10-30 4:10 Skip Tavakkolian
2002-10-30 6:29 Russ Cox
2002-10-30 11:06 ` Boyd Roberts
2002-10-30 8:31 Charles Forsyth
2002-10-30 13:14 ` rob pike
2002-10-30 14:16 ` Jim Choate
2002-10-30 8:55 okamoto
2002-10-30 9:37 C H Forsyth
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
2002-10-30 20:34 ` Dan Cross
2002-10-30 15:42 Skip Tavakkolian
2002-10-30 17:21 Russ Cox
2002-10-30 21:55 ` Jim Choate
2002-10-30 18:21 rob pike, esq.
2002-10-30 22:00 ` Jim Choate
2002-10-31 2:59 okamoto
2002-10-31 5:18 ` 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 5:15 okamoto
2002-10-31 6:35 ` Jim Choate
2002-10-31 5:26 okamoto
2002-10-31 14:38 Skip Tavakkolian
2002-11-04 18:38 ` Peter Downs
2002-11-05 18:47 ` Dan Cross
2002-11-04 15:15 Skip Tavakkolian
2002-11-04 18:49 Charles Forsyth
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=Pine.LNX.4.33.0210292347110.15595-100000@einstein.ssz.com \
--to=ravage@einstein.ssz.com \
--cc=9fans@cse.psu.edu \
--cc=hangar18-general@open-forge.org \
/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).