Confirmed users
496
edits
Remote Debugging Protocol: Difference between revisions
Jump to navigation
Jump to search
→Packets: Refine no-such-actor response.
m (→Listing Top-Level Browsing Contexts: Note flaws in browsing-context / thread relationship.) |
(→Packets: Refine no-such-actor response.) |
||
| Line 43: | Line 43: | ||
If a packet is directed to an actor that no longer exists, the server sends a packet to the client of the following form: | If a packet is directed to an actor that no longer exists, the server sends a packet to the client of the following form: | ||
{ "from": | { "from":<i>actor</i>, "error":"no-such-actor" } | ||
where <i>actor</i> is the name of the non-existent actor. (It is strange to receive messages from actors that do not exist, but the client evidently believes that actor exists, and this reply allows the client to pair up the error report with the source of the problem.) | |||
Clients should silently ignore packet properties they do not recognize. We expect that, as the protocol evolves, we will specify new properties that can appear in existing packets, and experimental implementations will do the same. | Clients should silently ignore packet properties they do not recognize. We expect that, as the protocol evolves, we will specify new properties that can appear in existing packets, and experimental implementations will do the same. | ||