Re: new code to help with cross-process windows/workers (and Clients API)

2017-12-09 Thread Ben Kelly
On Dec 9, 2017 8:25 AM, "Gijs Kruitbosch" wrote: On 08/12/2017 20:23, Ben Kelly wrote: > Please let me know if you have any question or if you think you have a > feature that could integrate with the clients infrastructure. While the > initial implementation is

Re: new code to help with cross-process windows/workers (and Clients API)

2017-12-09 Thread Gijs Kruitbosch
On 08/12/2017 20:23, Ben Kelly wrote: Please let me know if you have any question or if you think you have a feature that could integrate with the clients infrastructure. While the initial implementation is limited to Clients API needs, I've tried to design it to support other internal uses.

Re: new code to help with cross-process windows/workers (and Clients API)

2017-12-08 Thread Ben Kelly
On Fri, Dec 8, 2017 at 4:38 PM, Mike Conley wrote: > >> I personally think this would be useful, and will (probably) only > happen if > >> you do it now, before you move on to the next thing. +1 for > documentation! > > I concur. > Alright. I'll work on a blog post next

Re: new code to help with cross-process windows/workers (and Clients API)

2017-12-08 Thread Mike Conley
This all sounds great! >> I personally think this would be useful, and will (probably) only happen if >> you do it now, before you move on to the next thing. +1 for documentation! I concur. ___ dev-platform mailing list dev-platform@lists.mozilla.org

Re: new code to help with cross-process windows/workers (and Clients API)

2017-12-08 Thread Nicholas Alexander
Hi Ben, On Fri, Dec 8, 2017 at 12:23 PM, Ben Kelly wrote: > Hi all, > > I just want to give you a heads up about some new infrastructure that is > landing in the tree. In particular, we now have: > 1. A central list of windows and workers for the entire browser in the >

new code to help with cross-process windows/workers (and Clients API)

2017-12-08 Thread Ben Kelly
Hi all, I just want to give you a heads up about some new infrastructure that is landing in the tree. In particular, we now have: 1. A central list of windows and workers for the entire browser in the parent process. This includes information on their origin, url, and what process they are