Project

General

Profile

Feature #15661

Milestone #15372: art multi-threading phase 1

Feature #15374: Modifying all framework-provided services to be thread safe.

Make TriggerNamesService thread safe

Added by Kyle Knoepfel over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
02/24/2017
Due date:
% Done:

100%

Estimated time:
8.00 h
Spent time:
Scope:
Internal
Experiment:
-
SSI Package:
art
Duration:

Description

Determine to what extent TriggerNames and TriggerNamesService are duplicated.

History

#1 Updated by Kyle Knoepfel over 2 years ago

  • Category set to Infrastructure
  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

The TriggerNames class was not used anywhere, and so it was removed with commit art:ce080fbd.

The only member function that was non-const was TriggerNamesService::loadPosMap, which was used only in the c'tor. Unfortunately, this member function had public access, so removing it is potentially a breaking change. I went ahead and removed it, and we will mark the removal as a breaking change.

Implemented with commit art:91d94b73.

#2 Updated by Kyle Knoepfel over 2 years ago

This service has no ActivityRegistry callbacks.

#3 Updated by Kyle Knoepfel over 2 years ago

  • Target version set to 1209

#4 Updated by Kyle Knoepfel about 2 years ago

  • Target version changed from 1209 to 2.07.01

#5 Updated by Kyle Knoepfel about 2 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF