News for hackers. Stuff that matters.
Re:Why HTTP/3 is eating the world by jrpelkonen on Thursday October 05, 2023 @09:06AM (#37778100)
It is possible that this is not a fault of the parser or tooling. In some cases, specifically when the video file is not targeted for streaming, the moov atom is at the end of the mp4. The moov atom is required for playback.
Re:Why HTTP/3 is eating the world by lazide on Thursday October 05, 2023 @09:22AM (#37778273)
Zip files are the same. At least it makes it easy to detect truncated files?
Re:Why HTTP/3 is eating the world by regularfry on Thursday October 05, 2023 @12:02PM (#37780348)
That's intentional, and it can be very handy. Zip files were designed so that you make an archive self-extracting. They made it so that you could strap a self-extraction binary to the front of the archive, which - rather obviously - could never have been done if the executable code followed the archive.

But the thing is that the executable can be anything, so if what you want to do is to bundle an arbitrary application plus all its resources into a single file, all you need to do is zip up the resources and append the zipfile to the compiled executable. Then at runtime the application opens its own $0 as a zipfile. It Just Works.

Re:Why HTTP/3 is eating the world by KMag on Thursday October 05, 2023 @01:59PM (#37781805)
Also, it makes it easier to append new files to an existing zip archive. No need to adjust an existing header (and potentially slide the whole archive around if the header size changes), just append the data and append a new footer.
Re:Why HTTP/3 is eating the world by lazide on Thursday October 05, 2023 @02:09PM (#37781945)
Interestingly, a useful strategy for tape too, though zip is not generally considered tape friendly.
Re:Why HTTP/3 is eating the world by athanagor2 on Friday October 06, 2023 @05:51AM (#37788793)
This is exactly what Justine Tunney's redbean does.