- From: Liam Quinn <liam@htmlhelp.com>
- Date: Mon, 30 Aug 1999 09:55:23 -0400
- To: Patrice Calve <patrice.calve@cactuscom.ca>, www-html@w3.org
At 08:39 AM 30/08/99 -0400, Patrice Calve wrote: > >Another advantage of having the Content-Type inside the code is that it >would permit us to send different media types within one "page". Or having >the browser to choose to view one or another. You can already do this without using any TYPE attribute. >A classic use of this feature would be for downloading files. Modern >software download sites have a web page explaining how to download and >install the file beeing sent, and will send the file to the client. This is >done usually via a REFRESH (or redirect) action. What if the beginning of >the HTML web page had a html content type instruction and at the end of the >page, an instruction that will send to the browser the file + it's content >type. How would this differ from the Refresh approach? >More than that, what if the user/browser could choose between different >formats of the file? Choose between a PDF, Doc or txt file? Choose between >specific version of the document/software/platform? Same thing goes for >video, music, etc. This is already possible without any TYPE attribute. -- Liam Quinn A Real Validator for Windows, http://arealvalidator.com/ Web Design Group, http://www.htmlhelp.com/
Received on Monday, 30 August 1999 09:54:50 UTC