Jordan Last

An update on my progress. I have 206 partial responses somewhat working. I am now able to load a video player into the default Chrome video view and skip around....

Only response data On Mon, Jan 17, 2022, 11:02 PM Paul Young ***@***.***> wrote: > @lastmjs can you clarify if you are only > working on streaming *response* data, or...

Uploads are easily chunked by the client, as can be seen by dfx being able to upload large file sizes

What I meant by that is it's easy enough to chunk even from a browser client when uploading. As I understand it the browser client would just need to do...

Yeah I agree that would be great. I think for now it might be best to move this functionality into the JS agent, and then arbitrary sized ingress messages I...

Just ran into a major issue. I've deployed the canister to production and filled it with assets, but partial responses aren't working in production. I wonder if the boundary nodes...

More info in this forum post, @jplevyak has said he will talk to the team and see about getting this addressed: https://forum.dfinity.org/t/boundary-node-http-response-headers/10747

Interesting, I wonder if the 206 status code is not supported then? On Wed, Feb 9, 2022, 4:59 PM Roman Belov ***@***.***> wrote: > @lastmjs Hi!) > I am testing...

Just a heads up, apparently I shouldn't have even tried to do this from the canister. Not sure if there is a consensus on the best way to go about...

@3cL1p5e7 I've done my own testing, and it looks like `206` status codes work in production along with any http response headers I've tried. It looks like the boundary nodes...