Zombie control by streamHTML

[conartist6]

The proposed method of declarative DOM updates is problematic in that it leaves the potential for many "zombie controllers" to be attached to the DOM at any given moment: each suspended on a promise but ready to start mutating the DOM again the moment the promise resolves.

What happens if a stream writer yields a promise that never resolves? Is that an unfixable memory leak?

What if many stream writers are attached to the same element -- can they get into a race condition with each other?

[noamr]

The proposed method of declarative DOM updates is problematic in that it leaves the potential for many "zombie controllers" to be attached to the DOM at any given moment: each suspended on a promise but ready to start mutating the DOM again the moment the promise resolves.

Can you be more specific? I am not sure I understand the problem.

What happens if a stream writer yields a promise that never resolves? Is that an unfixable memory leak?

What promise? Example code maybe?

What if many stream writers are attached to the same element -- can they get into a race condition with each other?

A user of this API can create a race condition if they really want to.
If multiple streams are connected to the same element, they append parsed nodes to that element in the same order the respective streams are written into.
IOW there is a new HTML parser associated with each streamHTML* call. It receives strings as input from wherever, and whenever it outputs a root node, that node is appended to the target of the stream.
This in itself is not racy in terms of threads because it's all still in the main thread. But applications can create logical race conditions with it if they try.

[conartist6]

What promise

The promise returned by the stream iterator's next method.

[conartist6]

I would say you've only solved the declarative problem if what the user describes or declares as the desired target state of the system becomes the state of the system. Since this doesn't do that it isn't a solution to declarative updating, it's really just imperative updating then

[noamr]

I would say you've only solved the declarative problem if what the user describes or declares as the desired target state of the system becomes the state of the system. Since this doesn't do that it isn't a solution to declarative updating, it's really just imperative updating then

Correct, streamHTML is not exactly declarative.