How about Content-type headers? Are they determined by the file extension automatically? Are they only needed in the HTML5 code? Are they an issue anywhere in this project using HTML5 (not Flash player)?
The most difficult question of all:Can I use an Electric Imp Agent to directly serve the file to the HTML5 page? I have sent the contents of a file this way before including the WAV headers. The path is binary clean so I don't have to BASE64 encode it.
I plan on doing it like this:http://www.w3schools.com/html/html5_audio.aspContent-type headers are not needed?
<audio controls> <source src="sound.wav" type="audio/wav"> <source src="sound.mp3" type="audio/mpeg">Your browser does not support the audio element.</audio>
<audio controls> If available and can play it, then play this one -----> sound.wavelse if not available or can't play the one above, try this one ----> sound.mp3if can't find or play either, display this message -------> Your browser does not support the audio element.</audio>
I know I don't have to use the Electric Imp.I want to use the Imp, for another related project.Can I serve the audio file from the Agent to my HTML5 webpage above?
Just specify them in the HTML5 code like above?
What if the wav file is coming from another host? How does it send the Content-type headers?
<audio controls> <source src="http://www.TheOtherServer.com/sound.wav" type="audio/wav"></audio>
Please enter a valid email to subscribe
We need to confirm your email address.
To complete the subscription, please click the link in the
email we just sent you.
Thank you for subscribing!
via Egeo 16