[Webkit-unassigned] [Bug 30897] Web Inspector: Support Debugging via HTTP Headers like FirePHP and FireLogger

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=30897


Christoph Dorn <christoph at christophdorn.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |christoph at christophdorn.com




--- Comment #4 from Christoph Dorn <christoph at christophdorn.com>  2010-05-06 15:05:51 PST ---
Hi, I am the author of FirePHP, FireConsole and Wildfire.

I have been working on a reboot for FirePHP for a while now and am getting to a
point where wider testing makes sense.

The main goal of the reboot was to split FirePHP into several projects that
will allow for wider use.

The new setup includes:

  - FirePHP: Server library for PHP
  - FireConsole: Language agnostic firefox extension
  - Wildfire: Communication protocol
  - Insight: Multi-language object encoding and rendering library

At the lowest level a debugger such as Web Inspector would integrate wildfire
(now a pure CommonJS package) and provide logging receivers that can be
targeted from the server. The receiver dictates the format of the message and
the simplest use-case would be to allow logging into the Web Inspector console.

The Insight library will sit on top of wildfire and provide a means to encode
nested object graphs on the server (via language and class/framework specific
encoders) and render these on the client via CommonJS modules. All clients need
to do in order to render objects is to provide a CommonJS compliant environment
for insight to run in and a DOM to render the result in. This functionality is
currently being incubated as part of FireConsole and will be refactored into
standalone libraries in the coming months.

The focus of wildfire is simply to transport ASCII text via headers (and other
channels in future) from one component to another. The ideal place to start for
Web Inspector would be to integrate wildfire and define one or more logging
targets along with the expected format for the messages (probably json to begin
with).

You can find the wildfire project here: http://github.com/cadorn/wildfire

There is currently a CommonJS implementation for sending and receiving and a
PHP implementation for sending messages. If the component protocol is too
specific by requiring a sender and receiver header one could easily define a
new protocol that allows for message headers only where the target and message
format is implied by the protocol.

The goal is to keep the number of protocols and message formats to a minimum to
reduce the burden on server library and client implementers and encourage
interoperability but there is no real prior art in this area that I am aware of
and a certain amount of experimentation is inevitable. The primary purpose of
wildfire in this regard is to provide a minimum framework for alternate
protocols to evolve without conflict (i.e. allow them to co-exist in the same
response)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.