1713438 - [meta] Implement MessageHandler architecture

Status: NEW

(Remote Protocol :: WebDriver BiDi, task)

Description

[Julian Descottes [:jdescottes]]

Meta to implement the CommandsHandler architecture initially described in https://docs.google.com/presentation/d/1iIcVlQkNPhTj7wos2WbGV-7EqK6Qbbd8Kay5OjvH3ck/edit#slide=id.gcdb79f24e4_0_6 and https://docs.google.com/document/d/1Of3ZhWIAwYXPezuG_hMpmTK7Nv1a9_E_VsnBWtD2nD8/edit#heading=h.fhzr3f7daxcl

The CommandsHandler architecture should allow to:

• reach any context relevant for either WebDriver BiDi or devtools (chrome window, content window, process, worker)
• spawn modules in any relevant layer (parent process, content process main thread, content process worker thread)
• support multiple sessions (eg one from WebDriver BiDi + one from DevTools)
• route commands from the parent process to any context
• intercept commands at any layer between the parent process and the destination
• persist and broadcast session data (eg list of events currently subscribed to)
• handle new contexts created during the session (eg new frame appearing)

Comment 1

[Julian Descottes [:jdescottes]]

Attachment: CommandsHandler_scenario_7.svg

Comment 2

[Julian Descottes [:jdescottes]]

Attachment: CommandsHandler_scenario_1.svg

Comment 3

[Julian Descottes [:jdescottes]]

Attachment: CommandsHandler_scenario_2.svg

Comment 4

[Julian Descottes [:jdescottes]]

Attachment: CommandsHandler_scenario_3.svg

Comment 5

[Julian Descottes [:jdescottes]]

Attachment: CommandsHandler_scenario_4.svg

Comment 6

[Julian Descottes [:jdescottes]]

Attachment: CommandsHandler_scenario_5.svg

Comment 7

[Julian Descottes [:jdescottes]]

Attachment: CommandsHandler_scenario_6.svg

Comment 8

[Julian Descottes [:jdescottes]]

Attachment: MessageHandler_scenario_1.svg

Comment 9

[Julian Descottes [:jdescottes]]

Attachment: MessageHandler_scenario_2.svg

Comment 10

[Julian Descottes [:jdescottes]]

Attachment: MessageHandler_scenario_3.svg