Files
react-native/ReactCommon/react/renderer/core/EventQueue.cpp
T
Samuel Susla ffa533a19d Add option to use unbatched queues only
Summary:
Changelog: [internal]

My suggestion is to simplify event dispatching to only two options, synchronous and asynchronous.

Why?
- Fabric has only been using one queue, `AsynchronousBatched`.
- Batching happens even on `AsynchronousUnbatched`. It just batches events until JS thread starts processing them instead of waiting for the main run loop.
- It will make it easier to reason about the code in the future once we start utilising different priorities for Concurrent Mode.

Reviewed By: JoshuaGross

Differential Revision: D28603472

fbshipit-source-id: 14e3a9c15a012c550dc16a044c31d722051a2bdc
2021-05-22 12:19:05 -07:00

147 lines
3.5 KiB
C++

/*
* Copyright (c) Facebook, Inc. and its affiliates.
*
* This source code is licensed under the MIT license found in the
* LICENSE file in the root directory of this source tree.
*/
#include "EventQueue.h"
#include "EventEmitter.h"
#include "ShadowNodeFamily.h"
namespace facebook {
namespace react {
EventQueue::EventQueue(
EventPipe eventPipe,
StatePipe statePipe,
std::unique_ptr<EventBeat> eventBeat)
: eventPipe_(std::move(eventPipe)),
statePipe_(std::move(statePipe)),
eventBeat_(std::move(eventBeat)) {
eventBeat_->setBeatCallback(
std::bind(&EventQueue::onBeat, this, std::placeholders::_1));
}
void EventQueue::enqueueEvent(RawEvent &&rawEvent) const {
{
std::lock_guard<std::mutex> lock(queueMutex_);
eventQueue_.push_back(std::move(rawEvent));
}
onEnqueue();
}
void EventQueue::enqueueUniqueEvent(RawEvent &&rawEvent) const {
{
std::lock_guard<std::mutex> lock(queueMutex_);
auto repeatedEvent = eventQueue_.rend();
for (auto it = eventQueue_.rbegin(); it != eventQueue_.rend(); ++it) {
if (it->type == rawEvent.type &&
it->eventTarget == rawEvent.eventTarget) {
repeatedEvent = it;
break;
} else if (it->eventTarget == rawEvent.eventTarget) {
// It is necessary to maintain order of different event types
// for the same target. If the same target has event types A1, B1
// in the event queue and event A2 occurs. A1 has to stay in the
// queue.
break;
}
}
if (repeatedEvent == eventQueue_.rend()) {
eventQueue_.push_back(std::move(rawEvent));
} else {
*repeatedEvent = std::move(rawEvent);
}
}
onEnqueue();
}
void EventQueue::enqueueStateUpdate(StateUpdate &&stateUpdate) const {
{
std::lock_guard<std::mutex> lock(queueMutex_);
if (!stateUpdateQueue_.empty()) {
auto const position = stateUpdateQueue_.back();
if (stateUpdate.family == position.family) {
stateUpdateQueue_.pop_back();
}
}
stateUpdateQueue_.push_back(std::move(stateUpdate));
}
onEnqueue();
}
void EventQueue::onBeat(jsi::Runtime &runtime) const {
flushEvents(runtime);
flushStateUpdates();
}
void EventQueue::flushEvents(jsi::Runtime &runtime) const {
std::vector<RawEvent> queue;
{
std::lock_guard<std::mutex> lock(queueMutex_);
if (eventQueue_.size() == 0) {
return;
}
queue = std::move(eventQueue_);
eventQueue_.clear();
}
{
std::lock_guard<std::mutex> lock(EventEmitter::DispatchMutex());
for (const auto &event : queue) {
if (event.eventTarget) {
event.eventTarget->retain(runtime);
}
}
}
for (const auto &event : queue) {
eventPipe_(
runtime, event.eventTarget.get(), event.type, event.payloadFactory);
}
// No need to lock `EventEmitter::DispatchMutex()` here.
// The mutex protects from a situation when the `instanceHandle` can be
// deallocated during accessing, but that's impossible at this point because
// we have a strong pointer to it.
for (const auto &event : queue) {
if (event.eventTarget) {
event.eventTarget->release(runtime);
}
}
}
void EventQueue::flushStateUpdates() const {
std::vector<StateUpdate> stateUpdateQueue;
{
std::lock_guard<std::mutex> lock(queueMutex_);
if (stateUpdateQueue_.empty()) {
return;
}
stateUpdateQueue = std::move(stateUpdateQueue_);
stateUpdateQueue_.clear();
}
for (const auto &stateUpdate : stateUpdateQueue) {
statePipe_(stateUpdate);
}
}
} // namespace react
} // namespace facebook