In HTML5, a URL (or a set of URLs) point at what you want the
user-agent to display. From the spec's point of view, you can insert
any protocol (that can be described by a URL) in there. You'll need it
to be supported by your user-agent, of course.
In practice, live streaming works with HTTP
On Wed, Sep 22, 2010 at 12:36 PM, Henri Sivonen hsivo...@iki.fi wrote:
In practice, live streaming works with HTTP and either Ogg or WebM in at
least Firefox
and Opera (maybe Chromium, too), since Ogg and WebM don't require the length
of the
video to be known in advance.
I run a HTML5
Henri Sivonen wrote:
In HTML5, a URL (or a set of URLs) point at what you want the
user-agent to display. From the spec's point of view, you can insert
any protocol (that can be described by a URL) in there. You'll need it
to be supported by your user-agent, of course.
In practice, live
I run a HTML5 streaming business. I use icecast to send Ogg with
Theora+Vorbis. It works splendidly in Opera and Firefox. Chromium has
some problems because they use ffmpeg which is not always that good
when decoding Theora, but if I use the old, bad versions of Theora, it
also works in
I don't know if it might be a noob question, maybe becouse I am noob. hehe
I work in a company that do live video streaming. We are using the rtmp
protocol to do this streaming. My question is about how HTML5 handles
streaming. Is there already a specific solution in HTML5 for this kind of
In HTML5, a URL (or a set of URLs) point at what you want the user-agent to
display. From the spec's point of view, you can insert any protocol (that can
be described by a URL) in there. You'll need it to be supported by your
user-agent, of course.
On Sep 21, 2010, at 12:15 , Pedro
On Wed, Sep 22, 2010 at 12:45 AM, Pedro Fernandes Steimbruch
pedrofsteimbr...@gmail.com wrote:
I don't know if it might be a noob question, maybe becouse I am noob. hehe
I work in a company that do live video streaming. We are using the rtmp
protocol to do this streaming. My question is
