[packaging-on-the-web] When is the SPF stream finished? Is Content-Length enough? (#18)

As there is no end marker of Streamable Package Format (SPF) - how do we know the stream is finished and there are no more files, and that the connection was not broken for other reasons?

This could presumably be solved at the HTTP level - but could also be an issue for the file format. How do I now a .pack file is not half-way written to disk?

In the [SPF examples](http://w3ctag.github.io/packaging-on-the-web/#package-header) there are no `Content-Length` header. Presumably this can be difficult to know in advanced for a truly streaming server, in which case `Transfer-Encoding` SHOULD be used with a chunked transfer coding.

See https://tools.ietf.org/html/rfc7230#section-3.3.3

---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/packaging-on-the-web/issues/18