WildFire headers

[Robert Kosten]

Hi,

maybe I'm missing something, but the wildfire.org page does not seem
to provide much information about the actual Wf-headers. From what I
see at the FirePHP protocol page, the Protocol header seems to
indicate the WildFire version, the Plugin header the library on the
server and the Structure one is like a namespace or public DTD
identifier for the transmitted data. All of them are just identifiers,
not actual URLs.

Can anyone confirm or clarify that? I'm interested in building small
scale support into my homebrew-toy framework, without using the
provided library (Hey, it's for fun, no need to be overly reasonable
and reuse other people's work :-P), so I gather that I should not
identify the Plugin as
"http://meta.firephp.org/Wildfire/Plugin/FirePHP/Library-FirePHPCore/0.3",
but rather my own
"http://namespaces.strictstandardconformance.org/Wildfire/0.1". Sadly
that means the FirePHP-Firefox-Plugin doesn't recognize the headers
any more. Either I'm misinterpreting the header or that's a bug in the
FirePHP-Firefox-Plugin (It does not seem to make sense to restrict
display/processing based on the server, you wouldn't ignore anything
structurally valid because the http-server identified as anything but
IIS either, right ?)

Yours,
Robert Kosten

[Christoph Dorn]

Robert Kosten wrote:
> maybe I'm missing something, but the wildfire.org page does not seem
> to provide much information about the actual Wf-headers. From what I
> see at the FirePHP protocol page, the Protocol header seems to
> indicate the WildFire version, the Plugin header the library on the
> server and the Structure one is like a namespace or public DTD
> identifier for the transmitted data. All of them are just identifiers,
> not actual URLs.

Correct. And in its current state, FirePHP is the only program using the
wildfire protocol. I will be publishing a new spec for wildfire in the
coming weeks. It is similar to the current one, but removes some of the
limitations in getting it to work with other programs.

> Can anyone confirm or clarify that? I'm interested in building small
> scale support into my homebrew-toy framework, without using the
> provided library (Hey, it's for fun, no need to be overly reasonable
> and reuse other people's work :-P), so I gather that I should not
> identify the Plugin as
> "http://meta.firephp.org/Wildfire/Plugin/FirePHP/Library-FirePHPCore/0.3",
> but rather my own
> "http://namespaces.strictstandardconformance.org/Wildfire/0.1". Sadly
> that means the FirePHP-Firefox-Plugin doesn't recognize the headers
> any more. Either I'm misinterpreting the header or that's a bug in the
> FirePHP-Firefox-Plugin (It does not seem to make sense to restrict
> display/processing based on the server, you wouldn't ignore anything
> structurally valid because the http-server identified as anything but
> IIS either, right ?)

The FirePHP extension is going to be replaced by
http://www.fireconsole.org/ very soon. The new extension has full
support for different server libraries identified by different headers.

You will be able to migrate with some simple refactoring as the protocol
and structure is similar.

Until the new extension and protocol is published you can simply use the
FirePHP headers as is.

Christoph