Remote Debugging Protocol: Difference between revisions

→‎Requests and Replies: Define "unrecognized-packet-type" error.
(→‎Thread Pauses: Add "debugger-statement" pause reason.)
(→‎Requests and Replies: Define "unrecognized-packet-type" error.)
Line 64: Line 64:


where <i>name</i> is a JSON string naming what went wrong, and <i>message</i> is an English error message. Error <i>name</i>s are specified by the protocol; the client can use the name to identify which error condition arose. The <i>message</i> may vary from implementation to implementation, and should only be displayed to the user as a last resort, as the server lacks enough information about the user interface context to provide appropriate messages.
where <i>name</i> is a JSON string naming what went wrong, and <i>message</i> is an English error message. Error <i>name</i>s are specified by the protocol; the client can use the name to identify which error condition arose. The <i>message</i> may vary from implementation to implementation, and should only be displayed to the user as a last resort, as the server lacks enough information about the user interface context to provide appropriate messages.
If an actor receives a packet whose type it does not recognize, it sends an error reply of the form:
  { "from":<i>actor</i>, "error":"unrecognized-packet-type", "message":<i>message</i> }
where <i>message</i> provides details to help debugger developers understand what went wrong: what kind of actor <i>actor</i> is; the packet received; and so on.


= Grips =
= Grips =
Confirmed users
496

edits