Open Bug 1502960 Opened 5 years ago Updated 1 year ago
Avoid IPDL class constructor the need to manually propagate the ID to our internal constructor
I'd much prefer to avoid the need to manually propagate in the ID to our internal constructor, but I think we can do that in a follow-up & I can help out with it :-) Specifically, in this system, it seems like the actor's channel is opened during the constructor call, while the way IPDL works within gecko, for the most part, is that the actor is constructed, and then the channel is opened. I think it's OK to not allow sending messages directly from the actor's constructor.
You need to log in before you can comment on or make changes to this bug.