POST data from fmp4ingest - what is the intent of the tool?

[benmesander]

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?

[RufaelDev]

The tools intent is to provide a sample implementation and/or simple test setup.

Yes the long running post was removed after the DASH Industry forum converged on using short running post in version 1.1.

The upload of MPD is not supported in the tool.

good point on the content type setting, I think this would be a good and easy thing to fix.

I pushed to set it to application/mp4 for push_markers and fmp4_ingest