Re: http://www.nokia.com/corporate/wap/future_wap.html

[nospam@thanx]

On Sun, 19 Sep 1999, Denis Barbier wrote:

> On 16 Sep 1999, Fritz Zaucker wrote:
> 
> > I had pointed this conflict out some days ago already and think it is
> > a potential problem. Of course you can tell your WAP users to name
> > their files something other than .wml and use whatever they (or you)
> > choose in your mime-type file. Not nice, though.
> > 
> > The lesson to learn is: never use three letter appreviations (thanks,
> > MS-DOS ...)
> 
> I agree with your last sentence, but i'm not sure there is a real
> problem. Smart browsers should allow the user to customize how
> to render certain mime-types (but i don't know whether they do).

Well, i read RFC2068 (HTTP/1.1) more carefully and found this:

============================================================
7.2.1 Type

   When an entity-body is included with a message, the data type of that
   body is determined via the header fields Content-Type and Content-
   Encoding. These define a two-layer, ordered encoding model:

          entity-body := Content-Encoding( Content-Type( data ) )

   Content-Type specifies the media type of the underlying data.
   Content-Encoding may be used to indicate any additional content
   codings applied to the data, usually for the purpose of data
   compression, that are a property of the requested resource. There is
   no default encoding.
   Any HTTP/1.1 message containing an entity-body SHOULD include a
   Content-Type header field defining the media type of that body. If
   and only if the media type is not given by a Content-Type field, the
   recipient MAY attempt to guess the media type via inspection of its
   content and/or the name extension(s) of the URL used to identify the
   resource. If the media type remains unknown, the recipient SHOULD
   treat it as type "application/octet-stream".
============================================================

This means that a conflict about suffix names must be resolved on the
server side, and not by the client.

But again this is not a real problem since WML accept any suffix name
for input files.

-- 
Denis Barbier
WML Maintainer

______________________________________________________________________
Website META Language (WML)                www.engelschall.com/sw/wml/
Official Support Mailing List                   sw-wml@engelschall.com
Automated List Manager                       majordomo@engelschall.com