-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Cross-thread URL.createObjectURL #46557
Comments
Yep, it would be good to see this updated. |
This would solve quite many things
But there are some other blockers atm that dose not even accept blob urls in There needs to be some central location (aka blob store) where it can keep track of which blobs do exist and how to access them from basically anywhere. |
Any way to work around this? What's the alternative way to do this instead of bloburl? Passing arraybuffers around? |
There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the
never-stale
|
There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment. For more information on how the project manages feature requests, please consult the feature request management document. |
What is the problem this feature will solve?
The blob url created with
URL.createObjectURL
is not accessible from the other threads when usingbuffer.resolveObjectURL
.The FileAPI defines that the blob url store is a per-agent setting: https://w3c.github.io/FileAPI/#url-model. A blob url created in the main thread should be accessible from the worker threads.
What is the feature you are proposing to solve the problem?
The blob url store should be shared across threads.
What alternatives have you considered?
This is explicitly documented as https://nodejs.org/api/url.html#urlcreateobjecturlblob:
We can keep this as is without the spec compliance.
The text was updated successfully, but these errors were encountered: