Closed Bug 1593938 Opened 5 years ago Closed 5 years ago

Implement frame target listening with a TargetList like API on the server side

Categories

(DevTools :: Framework, enhancement, P2)

enhancement

Tracking

(Fission Milestone:M6)

RESOLVED DUPLICATE of bug 1593937
Fission Milestone M6

People

(Reporter: ochameau, Unassigned)

References

Details

Bug 1471754 introduced "LegacyImplementation" for each target type.
This is legacy as it depends on the existing listProcesses, listRemoteFrames, listWorkers methods and processListChanged, workerListChanged events.
This is considered legacy as these methods do not match frontend needs and force to fetch the full list of all the targets everytime one is created or destroyed.

Instead, the actors should expose an API that match the TargetList API:

  • startListening or watchTargets in order to declare that we want to receive all the targets of a given type. This will automatically emit all already existing targets. And then emit an event everytime there is a new target of this type being created or destroyed.
  • stopListening or unwatchTargets, which unregister the listener and stop emitting creation or destruction events.

This work should most liekly be done by keeping the LegacyImplementations in order to support backward compatibility.

Priority: -- → P2
Whiteboard: dt-fission-m2-mvp

Tracking for Fission Nightly (M6)

Fission Milestone: --- → M6

This is going to be implemented in bug 1593937.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Whiteboard: dt-fission-m2-mvp
You need to log in before you can comment on or make changes to this bug.