Method execute_or_enqueue

dds/DCPS/ReactorTask.cpp:394–431

}

ReactorTask::CommandPtr ReactorTask::execute_or_enqueue(CommandPtr command)
{
  OPENDDS_ASSERT(command);

  GuardType guard(lock_);

  // Only allow immediate execution if running on a reactor thread, otherwise we risk deadlock
  // when calling into the reactor object.
  const bool is_owner = reactor_owners_.find(ACE_Thread::self()) == EXIT_SUCCESS;

  // If state is set to processing, the contents of command_queue_ have been swapped out
  // so immediate execution may run jobs out of the expected order.
  const bool is_not_processing = !processing_;

  // If the command_queue_ is not empty, allowing execution will potentially run unexpected code
  // which is problematic since we may be holding locks used by the unexpected code.
  const bool is_empty = command_queue_.empty();

  // If all three of these conditions are met, it should be safe to execute
  const bool is_safe_to_execute = is_owner && is_not_processing && is_empty;

  // Even if it's not normally safe to execute, allow immediate execution if the reactor is shut down
  const bool immediate = is_safe_to_execute || (state_ == STATE_SHUT_DOWN);

  // Always set reactor and push to the queue
  ACE_Reactor* local_reactor = reactor_;
  command_queue_.push_back(command);

  // But depending on whether we're running it immediately or not, we either process or notify
  if (immediate) {
    process_command_queue_i();
  } else if (!reactor_notified_) {
    reactor_notified_ = true;
    guard.release();
    local_reactor->notify(this);
  }
  return command;
}

void ReactorTask::wait_until_empty()
{