diff options
| author | Nirbheek Chauhan <nirbheek@centricular.com> | 2014-08-18 14:56:56 (GMT) |
|---|---|---|
| committer | Nirbheek Chauhan <nirbheek@centricular.com> | 2014-08-18 14:56:56 (GMT) |
| commit | aeb78c6cb31cd638b0a7dd92de3b9817ced53eb5 (patch) | |
| tree | dea50013d80fc8140ec0f3c75c5a20a3aa3f8e0e /README | |
| parent | 281222987d800e76049d4667a7bdd6b4a8f20660 (diff) | |
| download | soup-transcoding-proxy-aeb78c6cb31cd638b0a7dd92de3b9817ced53eb5.zip soup-transcoding-proxy-aeb78c6cb31cd638b0a7dd92de3b9817ced53eb5.tar.gz | |
server: Add /stream/ prefix for streaming URLs
Diffstat (limited to 'README')
| -rw-r--r-- | README | 16 |
1 files changed, 8 insertions, 8 deletions
@@ -14,7 +14,7 @@ Usage with curl: ---------------- > Sending a stream (PUT) for only HTTP GET streaming: - $ curl -v "http://localhost:8000/[sessionid]?type=http" -T - < [video file] + $ curl -v "http://localhost:8000/stream/[sessionid]?type=http" -T - < [video file] This will use Chunked encoding and send the file in chunks. Optionally, you can rate limit to emulate a live stream (--limit-rate) @@ -22,18 +22,18 @@ Trying to create two streams on the same path will return a 409. > Reading the webm output stream (GET): - $ curl -v "http://localhost:8000/[sessionid]" > [output file] + $ curl -v "http://localhost:8000/stream/[sessionid]" > [output file] The server supports multiple PUT requests on different paths, and multiple GET requests from these paths. > Sending a stream (PUT) for only RTP-UDP streaming to 127.0.0.1:5004: - $ curl -v "http://localhost:8000/[sessionid]?type=rtp-udp&udp-clients=127.0.0.1:5004" -T - < [video file] + $ curl -v "http://localhost:8000/stream/[sessionid]?type=rtp-udp&udp-clients=127.0.0.1:5004" -T - < [video file] > Sending a stream (PUT) for both RTP-UDP and HTTP GET streaming: - $ curl -v "http://localhost:8000/[sessionid]?type=rtp-udp,http&udp-clients=127.0.0.1:5004" -T - < [video file] + $ curl -v "http://localhost:8000/stream/[sessionid]?type=rtp-udp,http&udp-clients=127.0.0.1:5004" -T - < [video file] > curl handles only HTTP, so there is no way to read the RTP-UDP stream using it @@ -43,7 +43,7 @@ Usage with souphttp: > Sending a stream from a file (PUT) for only HTTP GET streaming: $ gst-launch-1.0 filesrc location=[video file] ! \ - souphttpclientsink location="http://localhost:8000/[sessionid]?type=http" + souphttpclientsink location="http://localhost:8000/stream/[sessionid]?type=http" This will use a persistent HTTP connection and Content-Length + Content-Range headers to send the stream data. @@ -51,11 +51,11 @@ headers to send the stream data. > Sending a stream from a file (PUT) for only RTP-UDP streaming: $ gst-launch-1.0 filesrc location=[video file] ! \ - souphttpclientsink location="http://localhost:8000/[sessionid]?type=rtp-udp&udp-clients=localhost:5004" + souphttpclientsink location="http://localhost:8000/stream/[sessionid]?type=rtp-udp&udp-clients=localhost:5004" > Reading a webm output stream (GET): - $ gst-launch-1.0 souphttpsrc location="http://localhost:8000/[sessionid]" ! \ + $ gst-launch-1.0 souphttpsrc location="http://localhost:8000/stream/[sessionid]" ! \ filesink location=[some output file] > Reading an RTP-UDP output stream: @@ -66,7 +66,7 @@ headers to send the stream data. > Sending a stream from a file (PUT) for both RTP-UDP and HTTP GET streaming: $ gst-launch-1.0 filesrc location=[video file] ! \ - souphttpclientsink location="http://localhost:8000/[sessionid]?type=rtp-udp,http&udp-clients=localhost:5004" + souphttpclientsink location="http://localhost:8000/stream/[sessionid]?type=rtp-udp,http&udp-clients=localhost:5004" "udp-clients" is a comma-separated list of UDP host:ports to broadcast the RTP stream to. |