From: "James A. Robinson" <jim.robinson@stanford.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gtk port
Date: Thu, 29 Jun 2000 23:03:36 -0700 [thread overview]
Message-ID: <200006300603.CAA03419@cse.psu.edu> (raw)
In-Reply-To: Message from Randolph Fritz <randolph@cyber-dyne.com> of "Thu, 29 Jun 2000 22:13:26 PDT."References: <20000629221326.B8523@cyber-dyne.com> <3.0.5.32.20000629191848.008e84c0@mail.real.com> <Pine.LNX.3.96.1000629203938.13050I-100000@einstein.ssz.com> <200006292202.SAA24290@cse.psu.edu> <20000629211635.261.qmail@nx.aichi-u.ac.jp> <200006292202.SAA24290@cse.psu.edu> <20000629155159.A7064@cyber-dyne.com> <3.0.5.32.20000629191848.008e84c0@mail.real.com> <randolph@cyber-dyne.com> <200006300133.VAA28726@cse.psu.edu> <20000629221326.B8523@cyber-dyne.com>
>
> On Thu, Jun 29, 2000 at 08:41:31PM -0500, Jim Choate wrote:
> > I must disagree here, for example:
> >
> > .../httpd/einstein.ssz.com/index.html
>
> But many sites aren't organized that way. :( The web's metadata format
> is more confused than FTP's.
Yes, in general I think it is a very poor protocol. It is very flexible
about the name and parameters you can use to request a resource, but
doesn't return a name/value indicating the canonical name of the resource
you are retrieving.
The problem, as you point out, is that many sites just aren't organized
like this. If you request
http://www.sciencemag.org/
You are not getting '/index.html' but '/index.dtl' with 'dtl' being a
homegrown dynamic template language like shtml. Naturally what the browser
sees is straight html (as with shtml), but the problems start to appear if
you want to cache the resource or refer to it by it's resource name.
If you cache it as '/index.html' then you will run into trouble when
you try and and do a 'HEAD /index.html' to see if it has been modified.
Our server will respond that it knows nothing about '/index.html'
Jim
next prev parent reply other threads:[~2000-06-30 6:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 18:04 Hiroki Tamakoshi
2000-06-29 10:56 ` Artem 'Thomas' Hlushko
2000-06-29 12:14 ` Hiroki Tamakoshi
2000-06-30 8:24 ` Artem 'Thomas' Hlushko
2000-06-30 10:15 ` Hiroki Tamakoshi
2000-06-30 13:35 ` Artem 'Thomas' Hlushko
2000-07-01 3:32 ` Berry Kercheval
2000-07-03 9:34 ` Dennis Ritchie
2000-06-30 14:28 ` Randolph Fritz
2000-07-03 9:36 ` Douglas A. Gwyn
2000-06-29 12:52 ` Wladimir Mutel
2000-06-29 21:44 ` arisawa
2000-06-29 22:02 ` James A. Robinson
2000-06-29 22:51 ` Randolph Fritz
2000-06-30 2:18 ` Skip Tavakkolian
2000-06-30 1:41 ` Jim Choate
2000-06-30 3:02 ` arisawa
2000-06-30 1:33 ` James A. Robinson
2000-06-30 5:13 ` Randolph Fritz
2000-07-03 9:34 ` Andy Newman
2000-06-30 6:03 ` James A. Robinson [this message]
2000-06-30 8:26 ` Jonathan Sergent
2000-06-30 0:57 arisawa
2000-06-30 5:08 ` Randolph Fritz
2000-06-30 12:24 rog
2000-06-30 14:45 bwc
2000-06-30 22:02 ` arisawa
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=200006300603.CAA03419@cse.psu.edu \
--to=jim.robinson@stanford.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).