<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 2010-09-11 03:40, Silvia Pfeiffer wrote:<br>
[snip...]<br>
<blockquote
cite="mid:AANLkTi=UCdcQB4A5awgR-cNbtHzgfZtmnqsV9bdDPNY5@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
And yeah, this kinda stretched beyond the scope of HTML5
specs, but you'd be swatting two flies at once, solving the
sniffing issue with <video> and <audio>, but also
the sniffing issue that every OS has had for the last couple
of um... decades?! (poke your OS/Filesystem colleagues and ask
them what they think of something like this.)<br>
Then again, HTML5 is kinda a OS in it's own right, being a app
platform (not to mention supporting local storage of databases
and files even), so maybe it's not that far outside the scope
anyway to define something like this?<br>
<font color="#888888">
<br>
-- <br>
Roger "Rescator" Hågensen.<br>
Freelancer - <a moz-do-not-send="true"
href="http://EmSai.net/" target="_blank">http://EmSai.net/</a><br>
<br>
</font></blockquote>
</div>
<br>
<br>
Is there a link to your BINID proposal? From reading this I
wonder: Would it entail having to re-write all existing files with
an extra identifier at the start?<br>
<br>
Silvia.<br>
<br>
</blockquote>
<br>
<a class="moz-txt-link-freetext" href="http://www.emsai.net/projects/binid/details/">http://www.emsai.net/projects/binid/details/</a><br>
(it really need to be rewritten as it's way to wordy and repetitive
to explain something so simple, I was planning to rewrite the
document later this fall but...)<br>
<br>
And to answer your question, unfortunately yes, but that is the only
way to solve the issue.<br>
Some current fileformats would allow such a binary id header to be
added without any issues (as they scan past ID3v2 or similar meta
information anyway).<br>
Most existing software would have no issues adding a check for such
a binary id, in the long run it will save CPU cycles also.<br>
Certain streaming/transfer protocols could be updated too, and this
is where <video> and <audio> could leap ahead.<br>
<br>
The thing is as I said, is that a browser could easily strip off the
binary id before passing it on, so a codec or a OS filesystem or
local software would be completely unaware,<br>
but in time they too would support it (hopefully).<br>
A serverside script (PHP or Python for example) could easily add the
binary id to the start of a file or stream when sent to the browser,
or even added to the file during transcoding.<br>
so even if the server or .htaccess is set to only
application/octet-stream proper file format identification would be
still possible by browser only checking the binary id header.<br>
<br>
<pre class="moz-signature" cols="72">--
Roger "Rescator" Hågensen.
Freelancer - <a class="moz-txt-link-freetext" href="http://EmSai.net/">http://EmSai.net/</a>
</pre>
</body>
</html>