9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@messagingdirect.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mothra
Date: Wed, 19 Jul 2000 09:27:29 +0000	[thread overview]
Message-ID: <86vgy33uej.fsf@gollum.esys.ca> (raw)
In-Reply-To: <200007181831.TAA12571@whitecrow.demon.co.uk>

>>>>> "Steve" == Steve Kilbane <steve@whitecrow.demon.co.uk> writes:

    Steve> The protocols should be separate. Whether it's something as
    Steve> simple as writing a URL to a ctl file and reading a page
    Steve> back from a data file, or something more subtle, I don't
    Steve> know, but the posting and fetching shouldn't have much of a
    Steve> clue about what to do with the result.

Exactly. An httpfs that just serves HTTP raw MIME content (and handles
caching).

We have to divorce HTTP from HTML. They're two distinct problems.

We should look at the 3rd edition mail system for clues on how
to layer an HTML reader on top of an HTTP fileserver. The mail
problem is very similar: MIME on top of IMAP. s/IMAP/HTTP/ using
the existing MUA tools and we're much of the way there. (Especially
if httpfs can export a file/directory structure comparable to how
the IMAP server does it. httpfs caching might in fact be mandatory
for this to be possible.)

--lyndon


  parent reply	other threads:[~2000-07-19  9:27 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-18 15:38 miller
2000-07-18 17:31 ` Steve Kilbane
2000-07-19  9:27   ` Chris Locke
2000-07-19  9:27   ` Lyndon Nerenberg [this message]
2000-07-19 11:45     ` Howard Trickey
2000-07-19 12:27       ` Lucio De Re
2000-07-19 19:45       ` Steve Kilbane
2000-07-19 21:42         ` Boyd Roberts
2000-07-20 16:34       ` Lyndon Nerenberg
2000-07-21  8:33         ` Tom Ivar Helbekkmo
2000-07-19 15:38   ` Andy Newman
  -- strict thread matches above, loose matches on Subject: below --
2003-10-28 16:38 [9fans] Re: we need help matt
2003-11-11 17:12 ` [9fans] mothra Richard Miller
2000-07-19 18:29 rob pike
2000-07-19 16:59 Randolph Fritz
2000-07-19 12:05 Réf. : " boyd.roberts
2000-07-19 12:31 ` [9fans] " Howard Trickey
2000-07-19 12:51   ` [9fans] " Lucio De Re
2000-07-19 12:41     ` Colin DeVilbiss
2000-07-18 18:33 Russ Cox
2000-07-18 18:26 forsyth
2000-07-18 22:15 ` Randolph Fritz
2000-07-19  9:28   ` Chris Locke
2000-07-19 15:23     ` Andy Newman
2000-07-18 13:37 rob pike
2000-07-18 13:15 Sape Mullender
2000-07-18 16:25 ` Holger Veit
2000-07-18 12:51 rob pike
2000-07-18 13:19 ` Lucio De Re
2000-07-18 12:49 rob pike
2000-07-18 12:48 rob pike
2000-07-19 15:22 ` Douglas A. Gwyn
2000-07-17 13:49 boyd.roberts
2000-07-17 16:56 ` Tom Duff
2000-07-17 17:18   ` Howard Trickey
2000-07-18  8:25     ` Michael Jeffrey
2000-07-18  8:25   ` Douglas A. Gwyn
2000-07-18  8:58     ` Lucio De Re
2000-07-18 10:48       ` Wladimir Mutel
2000-07-18 11:37         ` Lucio De Re
2000-07-18 12:46           ` Wladimir Mutel
2000-07-19 15:23         ` Andy Newman
2000-07-18 18:11       ` Randolph Fritz
2000-07-19 15:22       ` Douglas A. Gwyn

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=86vgy33uej.fsf@gollum.esys.ca \
    --to=lyndon@messagingdirect.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).