Closed Bug 1482990 Opened 6 years ago Closed 6 years ago

Use different message names for inbound/outbound message between console and netmonitor actors.

Categories

(DevTools :: Netmonitor, enhancement, P3)

enhancement

Tracking

(firefox63 fixed)

RESOLVED FIXED
Firefox 63
Tracking Status
firefox63 --- fixed

People

(Reporter: ochameau, Assigned: ochameau)

References

Details

Attachments

(1 file)

Followup to bug 1479524:

(In reply to Julian Descottes [:jdescottes][:julian] from comment #8)
> Comment on attachment 8996280 [details]
> Bug 1479524 - Always use message manager with NetworkMonitorActor.
> ::: devtools/server/actors/network-monitor.js:145
> (Diff revision 4)
> >      }
> >    },
> >  
> >    onGetNetworkEventActor({ data }) {
> >      const actor = this.getNetworkEventActor(data.channelId);
> > -    this.messageManager.sendAsyncMessage("debug:get-network-event-actor", actor.form());
> > +    this.messageManager.sendAsyncMessage("debug:get-network-event-actor", {
> 
> Not related to your change, but I am a bit confused by the messages passed
> around with the message manager. If I understand correctly, the webconsole
> actor sends "debug:get-network-event-actor", here the network-monitor
> listens to this message and responds to is with another
> "debug:get-network-event-actor" but this time to return the result? Would it
> make sense to have different names here, maybe with kind of naming pattern?
> "debug:something-something-request" "debug:something-something-result"
Comment on attachment 9004807 [details]
Bug 1482990 - Use different message names for inbound/outbound message between console and netmonitor actors. r=jdescottes

Julian Descottes [:jdescottes][:julian] has approved the revision.
Attachment #9004807 - Flags: review+
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f6b4091debb4
Use different message names for inbound/outbound message between console and netmonitor actors. r=jdescottes
https://hg.mozilla.org/mozilla-central/rev/f6b4091debb4
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: