From: chad <y@mit.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Typesetting
Date: Tue, 16 Jan 2001 21:54:58 -0500 [thread overview]
Message-ID: <200101170255.f0H2twg01506@egon> (raw)
In-Reply-To: Your message of "Tue, 16 Jan 2001 17:37:46 EST." <200101162237.RAA05988@augusta.math.psu.edu>
> Well, I disagree that it simplifies something which is already simple.
> Consider creating ``sessions'' over HTTP as an example; I think the
> methods to do this are ad hoc and complex, if not entirely broken.
> Using file semantics makes this much easier.
I agree that the current methods for HTTP sessions are poor, but I
don't see how file/filesystem semantics improves the situation. Care
to explain?
> Regarding intermediate nodes caching so much, yes, this is true, but if
> intermediate nodes use an LRU mechanism to maintain the cache, I'm
> willing to bet that very heavily used sites will stay in a lot of
> caches for a lot of the time (I have no empirical evidence to back that
> up, obviously). What's more, there are fewer intermediate nodes
> contacting the origin site, which would have an effect on the system's
> overall scalability.
From a previous life, I can tell you that most caches have very high
hit rates, typically better than 90%. I don't have any data from the
past year or so, though, and heavily `interactive' content is
typically not cached.
> People seem bent on making the thing interactive, even though it wasn't
> built with that in mind.
I claim that people want to make the thing interactive because,
technical qualities aside, the web managed to be the first easily
cross-platform communications means in the burgeoning Internet. On
the other hand, it seems to be a common pattern for certain classes of
systems; take a look at the specification for Gopher+ sometime. (for
amusement's sake :-)
chad
next prev parent reply other threads:[~2001-01-17 2:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 2:09 William Staniewicz
2001-01-10 23:32 ` Dan Cross
2001-01-12 0:31 ` Steve Kilbane
2001-01-16 22:37 ` Dan Cross
2001-01-17 2:54 ` chad [this message]
2001-01-17 12:33 ` Micah Stetson
2001-01-17 20:52 ` Dan Cross
2001-01-17 23:05 ` Steve Kilbane
2001-01-22 18:00 ` Dan Cross
2001-01-11 9:50 ` Douglas A. Gwyn
2001-01-11 10:06 ` Boyd Roberts
2001-01-11 18:32 ` Dan Cross
2001-01-12 9:32 ` Randolph Fritz
-- strict thread matches above, loose matches on Subject: below --
2001-01-11 4:03 okamoto
2001-01-10 18:34 forsyth
2001-01-10 17:47 rob pike
2001-01-10 17:24 Laura Creighton
2001-01-10 17:34 ` Boyd Roberts
2001-01-10 19:58 ` Dan Cross
2001-01-12 9:32 ` Andy Newman
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=200101170255.f0H2twg01506@egon \
--to=y@mit.edu \
--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).