-
Notifications
You must be signed in to change notification settings - Fork 136
DASH: rely on "txml" parser for Multithreading usages #1384
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
Merged
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
71a25e3
[POC]: Experiment with "txml" parser, to get rid of the DOMParser
peaBerberian 4579511
Parse xml entities
peaBerberian fe92987
DASH: Begin translating unit tests
peaBerberian dce924c
Move files around and fix parseFromDocument tests
peaBerberian 69c1d83
DASH: rewrite unit tests
peaBerberian c849efb
Handle EventStream events
peaBerberian 89f2e1c
Add both DOM and fastjs parser
peaBerberian 9238d1a
Parse xml inside fast js parser
peaBerberian 1707042
Rely on JS parser in multithread mode by default
peaBerberian 5e07364
Fix failing integration test
peaBerberian 66605c6
Add unit test for xml parser
peaBerberian 4bf4fc8
Fix code style after review
peaBerberian f3b92a1
Remove DASH js feature from features/list for now
peaBerberian b6c2166
doc: update Multithreading documentation as embedded wasm isnt a requ…
peaBerberian fded006
Do not fallback if WebAssembly initialization fails
peaBerberian File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason to prefer assigning those property over calling the exposed methods in
src/features/listlikeaddDashFeature,dashWasmFeature.. ?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good question and I've thought about it.
However it seems that features exported in
src/features/list, because they are the exact same files imported by applications, assume a main thread environment. This is to reduce the number of features to import for an application (the end goal being a simpler API).As such, importing
src/features/lib/dash.tsalso adds aMediaSourceContentInitializerto play content in main thread and aMainCodecSupportProberto perform codec checks on main thread.Because we don't want those in a worker, in the end I kept just manually selecting the exact feature we want in
worker_main.ts