[9986] in www-talk@info.cern.ch
Re: Implementation of negotiated content
daemon@ATHENA.MIT.EDU (Koen Holtman)
Thu May 16 16:56:23 1996
From: koen@win.tue.nl (Koen Holtman)
To: jjb@sequent.com (Jeff Berkowitz)
Date: Thu, 16 May 1996 22:47:14 +0200 (MET DST)
Cc: www-talk@w3.org
In-Reply-To: <199605161834.LAA04950@eng5.sequent.com> from "Jeff Berkowitz" at May 16, 96 11:34:49 am
Resent-From: www-talk@w3.org
Jeff Berkowitz:
>
>Does anyone have any knowledge, speculation, or just plain WAGs
>about how real HTTP 1.1 servers will implement content negotiation?
Apache already has some mechanisms for it, and I believe Spyglass has
something too. I qoute a part of an Apache documentation web page below. I
took this from my archive, and have no URL, but you can of course use a
search engine to find the whole page.
Koen.
--snip--
[INLINE]
Module mod_negotiation
This module is contained in the mod_negotiation.c file, and is
compiled in by default. It provides for content negotiation. Any
document with mime type application/x-type-map will be processed by
this module.
Summary
Content negotiation, or more accurately content selection, is the
selection of the document that best matches the clients capabilities,
from one of several available documents. There are two implementations
of this.
* A type map (a file with the mime type application/x-type-map)
which explicitly lists the files containing the variants.
* A MultiViews search (enabled by the MultiViews Option, where the
server does an implicit filename pattern match, and choose from
amongst the results.
