DevTools/Features/Debugger: Difference between revisions

DevTools/Features/Debugger (view source)

Revision as of 00:59, 6 May 2011

1,462 bytes added , 6 May 2011

Added planning subsection for the basic protocol implementation.

DCamp

Confirmed users

673

edits

@@ Line 48: / Line 48: @@
 TBD
+== Planning ==
+The following is not complete.
+=== Basic Protocol Support ===
+Implementation of the [[Remote Debugging Protocol]].
+=== Protocol Transports ===
+* Simple TCP socket protocol - Needed for remote debugging.
+* Shouldn't need sockets for in-process debugging, can probably just post events directly to/from the handler thread.
+* Need to figure out transport between chrome/content for e10s (See inter-process dispatch, below).
+* WebSockets (not needed for an initial implementation).
+=== Protocol Handler Thread ===
+* Handles incoming protocol requests on a thread, needed to interrupt running script on other threads.
+* Will handle transport IO as needed (for socket/websocket/etc transports).
+* Handle inter-thread dispatching
+** Dispatching incoming protocol messages to actors on the proper thread.
+** An actor's parent or child might be on a different thread (for example when a browser tab actor might have a WebWorker actor as a child).  Releasing a parent actor needs to release children, including on the other threads.
+* Handle inter-process dispatching
+** Similar issues to inter-thread dispatch, but communicating to content processes using the debugging protocol.
+=== Actor registration API ===
+* Including maintenance of the actor tree.
+=== Debugging compartments ===
+* The debugger must be in a separate compartment from the debuggee, some sort of sandbox/new global-and-compartment for hosting a given thread's debugging actors.
 __NOTOC__