You cannot post messages because only members can post, and you are not currently a member.
Description:
Discuss, design, develop a remote debug protocol for Web-based applications. The core idea is a protocol that would support a Firebug-like user interface client attached to a web-browser-like runtime server. Variations, sub and super sets, library design, all related ideas welcome.
|
|
|
Crossfire - Remote Debug Extension for Firebug
|
| |
Hello,
I thought the Web Debug group might like to know that I've committed
an extension, called "Crossfire", to the Firebug project.
Crossfire implements a JSON format protocol, which at the moment is
somewhat of a hybrid of the V8 and Scope specs, with a few additions
of its own.
One important aspect of Crossfire is to allow a remote client to... more »
|
|
Debug Commands and Arguments
|
| |
From comparing the various javascript debugging protocols I've noticed
that the commands for the debug operations ("break", "continue",
"setbreakpoint") have very little variance across protocols, for the
most part. However the arguments and parameters for many of the
commands do vary to a greater degree, so one of the things I have been... more »
|
|
Introduction
|
| |
Hi folks, my name is Attila Szegedi, and -- among other things -- I'm working on a remote debugger architecture for Mozilla Rhino (JavaScript implementation for the JVM). I did serve as the project maintainer for Rhino for some time, and am still a committer to the project. The background for my debugger involvement is that at my day job, we... more »
|
|
Web Debug Protocols Comparison
|
| |
Since Opera's Scope protocol has now been announced, I wanted to
understand how it compared to V8 and DBGP for Web debugging, so I
tried to put together a quick comparison of features, which I've
uploaded here:
[link]
First impressions are that Scope has much more complete support for... more »
|
|
Opera Scope protocol specification has just been released
|
| |
Hi,
I’m the Product Manager of Opera Dragonfly – Opera’s developer tools.
When we set about the task of building debugging tools for Opera, we
needed a protocol to be able to communicate between the developer
tools and the underlying rendering engine. As Opera is available for
many platforms we needed to make sure that this protocol could... more »
|
|
Packet Formats (and HTTP/Socket proxy)
|
| |
In the discussion of protocol layers, there were arguments made in
favor of both socket-based and HTTP based protocols, though not much
objection to JSON as a data format. Simon Kaegi brought up the
possibility of using two transports, and I don't see why this
shouldn't be possible. I think we will need to put some stakes in the... more »
|
|
Abstract Web Machine
|
| |
One of the areas where we have good potential for collaborative work
and cross-browser implementation is in an API for describing the web
runtime. The idea is to have a description of the runtime independent
of its implementation. The W3C standards already define most of the
runtime API in a (more-or-less) browser-independent way. We just need... more »
|
|
Protocol layers; a vote for JSON/HTTP
|
| |
The connection between user interface (client, consumer) and runtime
(server, producer) has several parts. Sorry if I don't use the
correct terminology below.
To set up the connection some choices are:
homebaked sockets
HTTP
Within the connection the data needs to be formatted:
binary,... more »
|
|
|