Updating coincident to its latest #109
Merged
Conversation
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
WebReflection
force-pushed
the
coincident-next
branch
16 times, most recently
from
4ff3f12 to
282d1cf
Compare
This was referenced Jul 24, 2024
WebReflection
force-pushed
the
coincident-next
branch
9 times, most recently
from
eacdbd1 to
e947ef4
Compare
WebReflection
force-pushed
the
coincident-next
branch
from
e947ef4 to
377accc
Compare
ntoll
approved these changes
Jul 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This version brings in latest coincident and sabayon features, most notably it allows main consuming worker utilities out of the box without needing any special header and it helps solving headers issues, when not possible or not desired to be defined via the server itself, through the new
service-worker="../sw.js"attribute that will orchestrate automatically a bootstrap able to consume SharedArrayBuffer in a way or another.The currently tested options, as ServiceWorker file content, are:
When one of these files are present in the project same folder or above (it can only be above current folder, never in a nested one) the logic either does fallback to native SharedArrayBuffer or it uses a sync request orchestration via sabayon (slowest, yet it doesn't have any other caveat attached).
A new
serviceWorkeroption has been added also to the proceduralXWorkerconstructor and everything has been tested in multiple browsers without issues.