Implementation of negotiated content

Does anyone have any knowledge, speculation, or just plain WAGs
about how real HTTP 1.1 servers will implement content negotiation?

The spec defines "generic resources", the "Accept" header, cache
behavior, and so on.  I'm interested in what the implementors of
origin servers will do.  E.g., an origin server might dictate that
generic resources be implemented as file system directories with
negotiable plain resources as files in those directories, or ... ?

Thanks,
Jeff Berkowitz jjb@sequent.com

Received on Thursday, 16 May 1996 14:35:53 UTC