Re: Possible use of <INSERT> - serious inquiry

Abigail (abigail@tungsten.gn.iaf.nl)
Tue, 19 Mar 1996 19:16:16 +0100 (MET)


From: Abigail <abigail@tungsten.gn.iaf.nl>
Message-Id: <199603191816.TAA09113@tungsten.gn.iaf.nl>
Subject: Re: Possible use of <INSERT> - serious inquiry
To: www-html@w3.org
Date: Tue, 19 Mar 1996 19:16:16 +0100 (MET)

Rainer Klute wrote:
++ 
++ >++ <insert
++ >++       type="text/html"
++ >++       data="http://www.mysite.com/path/file.html"
++ >++ >
++ >++ </insert>
++ >++ 
++ >++ If it isn't possible, wouldn't this be a worthwhile extension to the 
++ >++ <INSERT> capability?
++ >
++ >I do not think so.  Using the http protocol, it is the _server_ which
++ >gives out the information about the document type. What should
++ >a user agent do if the <insert> type says 'image/gif', but
++ >the server gives 'image/jpg'? What if the type isn't fixed in advance?
++ >How would you do it with content negotiation?
++ 
++ I think the original approach fits very well with content
++ negotiation. The attribute type="text/html" is indeed a content
++ negotiation, since the client requests a piece of data in
++ text/html format. If the server couldn't deliver it in the
++ requested format it shouldn't deliver anything.

But that's just _against_ content negotiation. With content
negotiation, the client tells the server which types it
can accept, or prefers to have. What's the point of telling the
client to ask for which type? Then there is nothing left
to negotiate.


Abigail

-- 
<URL: http://www.edbo.com/abigail/>  (Changed)