Only send changes across state message channels about webext-redux HOT 7 CLOSED

In Opentest's Chrome extension, we send updates of the audio stream frequency data if our audio visualizer bar is showing in the UI.

The delta of the state is small (just one byte array of length the number of bars in the visualizer), but the updates are very frequent. Just leaving this here for myself so I can look at the performance impact from the dev console to see how the following two things are impacted as the state size grows/shrinks:

1. Serializing/deserializing the state.
2. Latency of sending the state over the port object.

We should actually make sure that diff-ing the object makes sense and doesn't itself introduce unnecessary overhead. The reason it works for react to diff DOM updates is because the DOM itself is slow. We simply have to validate that here with larger messages over the port object.

from webext-redux.

Sounds like a great test case. Looking forward to seeing the results.

I couldn't agree more with you. We definitely shouldn't implement this willy-nilly. We should test this proposal against multiple use cases (frequency and state size).

from webext-redux.

Found some analog for this:
https://github.com/ivantsov/redux-webext

from webext-redux.

@sidoruk-sv Do you mind expanding on your comment a bit more? From what I can tell, that package uses the same method as react-chrome-redux.

from webext-redux.

@tshaddix oh, I see, thought they implement lightweight messages to background's store, but now I see that it's very similar to this library, i'm sorry)
Will try to use your library for my pet project. Thank you for comment!)

from webext-redux.

@sidoruk-sv if you'd like to see an extension in the wild that uses this library, check out the Openvid extension:

https://chrome.google.com/webstore/detail/openvid-screen-recorder-c/liecbddmkiiihnedobmlmillhodjkdmb

from webext-redux.

Included in #100

from webext-redux.