I arrived here from the sample code in https://github.com/Dash-Industry-Forum/Ingest
I noted that the fmp4ingest tool uses a POST with a content type of application/x-www-form-urlencoded. This is undesirable, because it basically triples the size of the segments posted, increasing latency, increases the complexity to use incrementally received data as it arrives, etc.
There is partially implemented (commented code) which appears to use chunked transfer coding for a "long running post", presumably the intent here is an "endless mp4" type upload.
What I was hoping to find was something that did application/octet-stream or similar and just uploaded the unadorned segment with a content-length header or chunked transfer encoding with a complete payload in one chunk. Is this what was intended, or was application/x-www-form-urlencoded the intent?
Also, I note that the tool does not upload an MPD file to go with the segments - is this intentional as well?
I arrived here from the sample code in https://github.com/Dash-Industry-Forum/Ingest
I noted that the fmp4ingest tool uses a POST with a content type of
application/x-www-form-urlencoded. This is undesirable, because it basically triples the size of the segments posted, increasing latency, increases the complexity to use incrementally received data as it arrives, etc.There is partially implemented (commented code) which appears to use chunked transfer coding for a "long running post", presumably the intent here is an "endless mp4" type upload.
What I was hoping to find was something that did
application/octet-streamor similar and just uploaded the unadorned segment with a content-length header or chunked transfer encoding with a complete payload in one chunk. Is this what was intended, or wasapplication/x-www-form-urlencodedthe intent?Also, I note that the tool does not upload an MPD file to go with the segments - is this intentional as well?