Platform/JSDebugv2: Difference between revisions

Platform/JSDebugv2 (view source)

Revision as of 01:18, 19 July 2010

97 bytes added , 19 July 2010

m

→‎Design Summary

Jimb

Confirmed users

496

edits

@@ Line 51: / Line 51: @@
 documentation.)</i>
-Debugger user interfaces communicate with the application being debugged via a [[Remote Debugging Protocol|remote debugging protocol]]. The protocol is JSON-based, with clients and servers typically implemented in JavaScript. The protocol is actor-oriented: each packet is directed to or received from a specific actor, representing a thread, breakpoint, JavaScript object, or the like.
+Debugger user interfaces communicate with the application being debugged via a [[Remote Debugging Protocol|remote debugging protocol]]. The protocol is JSON-based, with clients and servers typically implemented in JavaScript. Each packet from the client is directed at a specific <i>actor</i> on the server, representing a thread, breakpoint, JavaScript object, or the like; each packet from the server comes from a specific actor.
-Every server provides a root actor that can provide global information about the application ("I am a web browser"), and enumerate the potential debuggees present in the application&mdash;tabs, worker threads, chrome, and so on&mdash;each represented by its own actor.
+Every server provides a root actor that can provide global information about the application ("I am a web browser"), and enumerate the potential debuggees present in the application&mdash;tabs, worker threads, chrome, and so on&mdash;each of which is represented by its own actor.
 Actors representing individual JavaScript threads use the jsd2IDebuggerService Web IDL interface to inspect and manipulate the debuggee they represent. jsd2IDebuggerService is an alternative to the existing jsdIDebuggerService, implemented in terms of the js::dbg2 C++ interfaces.
-The code implementing thread actors runs in the threads they represent; the server routes debugging protocol packets to actors appropriately. All inter-thread communication is handled this way, so thread actors and the interfaces they use can be single-threaded.
+The code implementing a thread actor runs on the thread it represents; the server routes debugging protocol packets to actors as needed. All inter-thread communication is handled this way, permitting thread actors and the interfaces they use to be single-threaded, and simplifying their implementation.
 The jsd2IDebuggerService Web IDL interface presents js::dbg2's facilities to JavaScript.  jsd2IDebuggerService is an alternative to the existing jsdIDebuggerService.