RUMM-2602: Use event write context in RUM #1117
Merged
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.
What does this PR do?
This change brings the usage of event write context (EWC) to RUM (and to Web View RUM) and is similar to the move done in #1106, #1103.
Basically to write RUM events we now first request EWC via
FeatureScope#withWriteContext
call. This call is done at the very last point, so that the switch to the worker thread (where the closure is executed) doesn't affect the sequential flow and no changes to the shared state is done from the closure context.There are some things which still keep RUM bound to the crash reporting or to the core feature (like the need to get server time offset outside of EWC, etc.), they will be addressed in the other PRs.
Review checklist (to be filled by reviewers)