Re: discovering site metadata

The upside is that it is pretty reasonable as far as saving
roundtrips. The downside is that people would have to configure their
servers to intercept OPTIONS * and do content negotiation on it. 

This should be easy-ish to do in Apache; not sure about IIS. In any
case it should be relatively easy to come up with a module that took
a special directory of site metadata files and made them available as
appropriate. 

I think it would have a decent chance of catching on if configuration
was fairly easy, and a few specs (like P3P and the Web Service
discovery thingy that was recently floated) adopted it. Fighting
against robots.txt will be hard...


On Thu, Dec 06, 2001 at 11:48:32PM -0600, Dan Connolly wrote:
> On Wed, 2001-12-05 at 20:43, Mark Nottingham wrote:
> [...]
> > The obvious solution would be to use OPTIONS * along with an
> > appropriate accept header (or maybe something like AcceptNS?).
> 
> er... not too obvious; I hadn't considered it before.
> 
> It's a nifty idea.
> 
> 
> 

-- 
Mark Nottingham
http://www.mnot.net/
 

Received on Friday, 7 December 2001 01:05:47 UTC