Native DOM receiver; receiver seam; mount knobs for benchmarking - #6
Merged
Conversation
NativeDomReceiver applies frames to the DOM directly: id map plus reverse WeakMap, createElementNS and setAttributeNS (SVG renders, which the remote-dom path cannot do), moveBefore for connected moves, template prototypes cloned with cloneNode, subtree walk on remove. The remote-dom transcoder stays as the interop receiver behind the same Receiver seam; the listener registry and template validator are shared. mount() gains receiver (native default) and transport (direct | chunked) options, an onChunk recording tap, stats (batches, frames, bytes) and nextCommit(). The e2e runs both demos against both receivers.
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
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.
NativeDomReceiver applies frames to the DOM directly: id map plus reverse
WeakMap, createElementNS and setAttributeNS (SVG renders, which the
remote-dom path cannot do), moveBefore for connected moves, template
prototypes cloned with cloneNode, subtree walk on remove. The remote-dom
transcoder stays as the interop receiver behind the same Receiver seam;
the listener registry and template validator are shared. mount() gains
receiver (native default) and transport (direct | chunked) options, an
onChunk recording tap, stats (batches, frames, bytes) and nextCommit().
The e2e runs both demos against both receivers.