Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Implement appendBuffer(blob) #185

Open
beaufortfrancois opened this issue Jun 21, 2017 · 10 comments
Open

Feature Request: Implement appendBuffer(blob) #185

beaufortfrancois opened this issue Jun 21, 2017 · 10 comments
Labels
feature request TPAC-2022-discussion Marked for discussion at TPAC 2022 Media WG meeting Sep 16
Milestone

Comments

@beaufortfrancois
Copy link

Is there's a technical reason why blob is not a valid source for appendBuffer()?
The immediate benefit I see to use blob is to not fetch the whole content at once into renderer memory like arrayBuffer does. It would be especially true in responses from the Cache API.

@jyavenard
Copy link
Member

Wouldn't that concern "not fetch the whole content at once into renderer memory like arrayBuffer does." a Blink only thing?

So far down the line, may be too late to add support for blob...

@calvaris
Copy link

IIRC at some point there was the intention of having appendBuffer taking a ReadableStream which would allow not loading the whole buffer in memory. I just checked the status of this and could not find it anywhere.

@jyavenard
Copy link
Member

I believe you mean appendStream... it was removed in #139

@paulbrucecotton
Copy link

Can we close this issue as a duplicate of ISSUE-14?

/paulc
HME WG Chair

@beaufortfrancois
Copy link
Author

@paulbrucecotton Do we have a rough ETA when to expect the next version of MSE (including appendStream())?

@paulbrucecotton
Copy link

The HME WG's charter currently only permits the WG to do maintenance on MSE. In Philippe's announcement it clearly states:

"As such, the Working Group is only allowed to make corrections that do not add new features [4] to its Recommendation(s) under this charter extension."

My suggestion is that those interested in the appendStream feature should "incubate" such a feature in a Community Group.

/paulc
HME WG Chair

@beaufortfrancois
Copy link
Author

Thank you @paulbrucecotton
@wolenetz Is that something you would be interested in?

@mayeaux
Copy link

mayeaux commented Dec 12, 2017

+1

@jakearchibald
Copy link

@calvaris

IIRC at some point there was the intention of having appendBuffer taking a ReadableStream which would allow not loading the whole buffer in memory

Rather than take a readable stream, it should expose a writable endpoint that you could pipe to.

I threw together a little demo of this at https://media-source-writable.glitch.me/, based on an example from @beaufortfrancois.

@mwatson2 mwatson2 added this to the Backlog milestone Sep 21, 2020
@mwatson2 mwatson2 added agenda Topic should be discussed in a group call feature request and removed agenda Topic should be discussed in a group call labels Sep 21, 2020
@wolenetz
Copy link
Member

See also #14, probably a duplicate if the approach is to add a writable endpoint to a SourceBuffer to which a stream/sequence of chunks could be piped.

@wolenetz wolenetz added the TPAC-2022-discussion Marked for discussion at TPAC 2022 Media WG meeting Sep 16 label Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request TPAC-2022-discussion Marked for discussion at TPAC 2022 Media WG meeting Sep 16
Projects
None yet
Development

No branches or pull requests

8 participants