9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mothra
Date: Tue, 18 Jul 2000 19:31:55 +0200	[thread overview]
Message-ID: <200007181831.TAA12571@whitecrow.demon.co.uk> (raw)
In-Reply-To: Your message of "Tue, 18 Jul 2000 16:38:59 -0000." <E13EZRk-000ElS-0V@anchor-post-31.mail.demon.net>

It seems to me that the reason why a web browser would be such a
behemoth is because current browsers try to do everything in one.
Breaking the problems down might produce something that's more
reasonable.

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

Since the spec keeps changing, maybe the returned page could be
translated into a local language that was more stable, and more
attuned to using a filesystem as the underlying namespace model
than URLs.

For doing the translation, perhaps a leaf could be
taken from troff's book, and have subcomponents of the page
translated into something else - the underlying, internal
language.

There's always going to be some sites (or parts of them) that
fall through the gap and don't work. But that's true now, for
everyone...

steve




  reply	other threads:[~2000-07-18 17:31 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 [this message]
2000-07-19  9:27   ` Chris Locke
2000-07-19  9:27   ` Lyndon Nerenberg
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=200007181831.TAA12571@whitecrow.demon.co.uk \
    --to=steve@whitecrow.demon.co.uk \
    --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).