Webm newbie

[Tim Müller]

On Thu, 2014-01-02 at 19:40 +0200, Vasileios Anagnostopoulos wrote:

Hi,

> the idea behind the golang application is that it listens on http port
> 9001 for path
> 
> 
> http://localhost:9001/stream.webm
> 
> 
> As soon s the browser connects, it sends the headers
> 
> 
> t := time.Now().UTC()
> w.Header().Set("Date", t.Format(layoutee))
> w.Header().Set("Connection", "Close")
> w.Header().Set("Cache-Control", "private")
> w.Header().Set("Content-Type", "video/webm")
> 
> and begins to listen on port 3005
> 
> 
> Then I start the pipeline and the server copies what it receives
> through port 3005 to the response body
> 
> 
> But after some bytes and without showing anything, either chromium or
> firefox closes the connection.
> 
> 
> I am on Windows 7 x86, gstreamer-1.0-x86-1.2.2, golang 1.2
> 
> 
> Is the rationale sane?

Yes something like that should work in principle.

Does it work with

  gst-launch-1.0 playbin uri=http://localhost:9001/stream.webm

?

If not, what is the output of:

  gst-launch-1.0 http://localhost:9001/stream.webm ! fakesink dump=true

? (First few lines of the hexdump should be enough.

Note that you can also use multifdsink or multisocketsink, and simply
add to it the socket of the client (and any other clients if it's a
shared stream), then it will output the data including headers directly
to that.

Cheers
 -Tim


-- 
Tim Müller, Centricular Ltd - http://www.centricular.com