Open Bug 1144227 Opened 9 years ago Updated 2 years ago

Properly document the async behavior of the Telemetry modules

Categories

(Toolkit :: Telemetry, defect, P4)

defect
Points:
1

Tracking

()

People

(Reporter: gfritzsche, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [measurement:client])

We have some async tasks and async startup and shutdown behavior for TelemetryPing.jsm and TelemetrySession.jsm.

We need to document this properly for future readers:
* more in-code commenting on the async parts/tasks and how they interact and order
* ideally an overview on the async/task/etc behavior in the in-tree docs

(Note that bug 1140558 will remove some asynchronicity)
Blocks: 1122482
No longer blocks: 1120356
Blocks: 1201022
No longer blocks: 1122482
The in-code commenting should be reasonable now, we still want to add a short overview of the Telemetry modules involved and the kind of tasks they run.
Points: --- → 1
Priority: -- → P3
Whiteboard: [measurement:client]
Priority: P3 → P4
Blocks: 1292530
No longer blocks: 1201022
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.