Bug 327005 - Ensure JSDI can be used in a round trip manner
Summary: Ensure JSDI can be used in a round trip manner
Status: RESOLVED FIXED
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.4 M7   Edit
Assignee: Michael Rennie CLA
QA Contact: Simon Kaegi CLA
URL:
Whiteboard:
Keywords: api, plan
Depends on: 326783
Blocks:
  Show dependency tree
 
Reported: 2010-10-05 09:41 EDT by Michael Rennie CLA
Modified: 2012-04-11 00:06 EDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2010-10-05 09:41:55 EDT 
We must make sure that JSDI can be used in a round-trip manner, such that:

1. You can connect to a remote client and control the client, and
2. you can connect back from a client and control the JSDT debugger

There are many examples of this desired use, two of the most notable being Firebug and ChromeDevTools, where you can connect, debug some code, and then perhaps change something in the browser and would like it to effect your client as well (the JSDT debugger).
Comment 1 Michael Rennie CLA 2011-04-28 16:12:14 EDT 
This work is on-going and being tested as we develop the Crossfire protocol for Firebug, but will not be complete for 3.3
Comment 2 Michael Rennie CLA 2012-04-11 00:05:42 EDT 
This work has been completed for Crossfire with bugs 363399 and 375652.

As there are no plans to add support for ChromeDevTools I am marking this issue fixed in 3.4M7