Open Bug 1687240 Opened 4 years ago Updated 4 years ago

Migrate all methods of NetworkEventActor to NetworkContentActor

Categories

(DevTools :: Netmonitor, task, P3)

task

Tracking

(Fission Milestone:Future)

Fission Milestone Future

People

(Reporter: ochameau, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-future)

For now, we moved only one method from NetworkEventActor to NetworkContentActor: getStackTrace, but we should move all of them in order to stop using DevToolsClient.request/WebConsoleFront for these requests:
https://searchfox.org/mozilla-central/rev/dac45cc7020dfddbcc937827810dd11550c07dc3/devtools/client/netmonitor/src/connector/firefox-data-provider.js#531-547

Here is the methods we should expose via NetworkContentActor:
https://searchfox.org/mozilla-central/rev/dac45cc7020dfddbcc937827810dd11550c07dc3/devtools/server/actors/network-monitor/network-event-actor.js#145-260
We may keep these methods on NetworkEventActor, but the ultimate goal, alongside bug 1687237 will be to make NetworkEventActor become just an helper class on the server, and no longer be an actor. This will still be used by NetworkEventWatcher and keyed by resourceId. But we will drop the notion of actor and front which is hard to maintain.

Adding into the M3 reserve list, so it isn't forgotten when we are planning a follow up Clean-up sprint.

Severity: -- → S3
Priority: -- → P3
Whiteboard: dt-fission-m3-reserve

Tracking dt-fission-m3-reserve bugs for Fission M8 (blocking Release channel experiment, but not Beta experiment).

Fission Milestone: --- → M8

Moving "dt-fission-m3-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.

Fission Milestone: M8 → Future
Whiteboard: dt-fission-m3-reserve → dt-fission-future
You need to log in before you can comment on or make changes to this bug.