Boundary node http response headers

Developers
50

I agree with your words!

About your suggestion: there are some limitations for boundary node:

  • The deploing own boundary node under custom domain is might be a great solution. But then it will lose the ability to work under ic0.app domain, especially when custom subdomains are released. Demergence-podcasts will live fine on demergence.com (for example), but not on potentially demergence.ic0.app.
  • This may can affect the audience’s trust (not a fact)
  • The streaming feature needs not only for demergence, it might be useful for others. And the easiest way to get streaming feature for ordinary developer is to use certified_assets canister (simple set "type"="assets" in your dfx.json and lets gooo)

In general, a solution is acceptable. Moreover, there is an info about deploy boundary node

@lastmjs
I’ve been thinking about this for the last week and can suggest the next:

  • In theory, you can to develop custom service-worker with range streaming support and register it on your canister manually. It will catch .raw. requests with range headers, will try to collect chunks from canister query methods and will return response with ranges to the client. There is my attempts to do this and it works nearly fine with TODOs for certfied_assets