- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Sat, 16 Apr 2016 00:36:19 +1200
- To: ietf-http-wg@w3.org
On 15/04/2016 11:26 a.m., Craig Pratt wrote: > Hello all, > > We have a use case where we are "live streaming" media over HTTP. As with other > (non-segmented) HTTP streaming applications, our live streaming solution has the > HTTP client perform a GET on a URI representing the live audio or video content > stream and with the server progressively returning data using chunked transfer > coding. The data returned to the server is "live" so long as the client reads > data as quickly as it's generated - with TCP flow control allowing the client's > reading of the response data to be paced to the live chunk generation of the > HTTP server. Please be careful not to rely on the chunks arriving at the client in the same sizes as were sent. The chunked encoding is a hop-by-hop feature so any HTTP intermediary which they travel through may re-code the chunk sizes according to its own output needs. Cheers Amos
Received on Friday, 15 April 2016 12:36:59 UTC