Re: &http-last-modified; (crazy idea of the day)

Lambert ([email protected])
Tue, 19 Dec 1995 17:50:12 -0400

>I like the idea, but the drift I'm getting is that entity names are
>to be associated with (HTTP) header field names ("Last-Modified" with
>`&http-last-modified;', "Access-Count" with `&http-access-count;', etc)
>and that I'm not so sure I like.

The http looks like a good idea, or maybe &meta-access-count, since they
ere meta headers, no necessarily by HTML.
> HTTP/1.0 200 Document Follows
> Last-Modified: Monday, 11-Dec-95 22:04:32 GMT
>
> <title>Arjun's First Reaction</title>
>
> <address><field http-equiv="Last-Modified"></address>
>
>will get the desired effect, provided we have a <FIELD> GI with attribute
>HTTP-EQUIV (NAME and CONTENT also maybe??) and EMPTY content, that can
>appear anywhere character-level markup is allowed.

Or how about:
HTTP/1.0 200 Document Follows
Last-Modified: Monday, 11-Dec-95 22:04:32 GMT

<title>Arjun's First Reaction</title>

<address><field http-equiv="Last-Modified">text inserted by normal
counters</field></address>

An old browser would ignore the <field> tags, and use the text and HTML
beteween them. You could do an old counter tht way. For the newer browsers,
they would not display the text between the <field> tags, and use the
original field tag. This would be similar to <NOFRAMES>

Mike