[Interest] Bringing Qt, C++ To The Web

[Jason H]

That is not a fair simplication of mime.
Base64 encoding anyone?
Chuncked-length encoding?




________________________________
 From: Mandeep Sandhu <mandeepsandhu.chd at gmail.com>
To: Nikos Chantziaras <realnc at gmail.com> 
Cc: "Interest at qt-project.org" <interest at qt-project.org> 
Sent: Friday, January 18, 2013 9:22 AM
Subject: Re: [Interest] Bringing Qt, C++ To The Web
 
>> OT, but isn't that done by examining file extensions or file headers
>> (like how the 'file' command works in Linux)?
>
> Once you've detected what the data is, you need to tell whomever asked
> about it what it actually is.  You need a communication protocol for
> that.  Like MIME.  So you get the request "what is this data?"  You look
> at it, and then answer "audio/mpeg", which is a MIME type.

Right, but MIME is not the communication protocol. That would be
something like HTTP. MIME just says: for xzy file type, use set the
content type to some standard string (like you mentioned).

-mandeep


>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest at qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20130118/6a72b235/attachment.html>