From: Vance S. <va...@mo...> - 2005-04-07 16:40:10
|
Klacke, It occurs to me that with the method I propose the server will need to remember the resource variant descriptions. For example out/1 returns: {alternates, [{"diagram.en.pdf", "0.9", [{type, "application/pdf"}, {language, "en"}]}, {"diagram.fr.pdf", "0.9", [{type, "application/pdf"}, {language, "fr"}]}, {"diagram.en.gif", "0.7", [{type, "application/pdf"}, {language, "en"}]}, {"diagram.fr.gif", "0.7", [{type, "application/pdf"}, {language, "fr"}]}]} After negotiation a request will be made for one of these binary files. Unless the server remembers the variant descriptions for these resources it will have to fallback to some other method to determine the appropriate Content-*: header fields. What do you think? In the Apache implementation the web author doesn't create the Alternates: header directly as I propose but instead creates a static file to define the Content-*: header fields for individual URIs. Alternatively the server is left to decide based on matching the file extensions. -Vance |