Ok, my diagram was mixing things up. It actually represents a number
This one is my proposed starting point: Bespin in one process
talking to Firebug+Firefox in another. This scenario allows us to
explore the full range of any web debug protocol, as much as bespin
cares to deal with. Mike Collins from IBM is prepared to contribute
code the the Firebug side of this based on his work with DBGP, that is
to port the DBGP part to a new protocol.
Firebug (chromebug actually) in one process and machine, Fennec in
another. Important case to get to soon.
Proxy debugging for Firefox. Not much drive for this one but almost
free from the Fennec use case.
Proxy debugging for V8. I guess the Chromium folks will have their
own debugger, so here the driver is more web devs who want one UI for
Here bespin has grown up and uses the same protocol without FIrebugs
In all of these cases the two ends of the wire are (probably) in
Hope this is clearer,
On Jun 12, 12:55 pm, Patrick Mueller <pmue...@gmail.com> wrote: