Re: Deploying new versions [Was: Versioning HTML at the

Terry Allen ([email protected])
Mon, 31 Oct 1994 07:03:00 PST

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Dave Kristol: "Re: An MGET proposal for HTTP"
Previous message: [email protected]: "Re: HTML Validation Form [Was: Nesting of HTML elements ]"
Next in thread: Gavin Nicol: "Re: Deploying new versions [Was: Versioning HTML at the"

If
> Content-type: text/html; version=3.0
won't work, then what is left aside from providing HTML documents
with a document type declaration (<!DOCTYPE line) and making
clients figure out the version after fetching the document
(rather wasteful if they can't render it)?

Regards,

-- 
Terry Allen  ([email protected])   O'Reilly & Associates, Inc.
Editor, Digital Media Group    Sebastopol, Calif., 95472
   			       [email protected]
A Davenport Group sponsor.  For information on the Davenport 
  Group see ftp://ftp.ora.com/pub/davenport/README.html

Next message: Dave Kristol: "Re: An MGET proposal for HTTP"
Previous message: [email protected]: "Re: HTML Validation Form [Was: Nesting of HTML elements ]"
Next in thread: Gavin Nicol: "Re: Deploying new versions [Was: Versioning HTML at the"