FirePHP with Nette Framework

[David Grudl]

I have implemented FirePHP native in Nette Framework a three months
ago. It is ideal solution for debugging AJAX application, thank you
for FirePHP!

- Nette Framework: http://nettephp.com 
- FirePHP usage: http://nettephp.com/cs/nette-debug-firebug
(in czech language yet)

Yesterday I have implemented FirePHP to database layer Dibi.

- Dibi: http://dibiphp.com 
- FirePHP usage: http://dibiphp.com/cs/profiler-a-propojeni-na-firebug

[David Grudl]

I have question - because my implementation is several months old it uses X-FirePHP-Data headers (see http://jdem.cz/afxh2). Is there any documentation for new format with X-Wf-... headers?

[Christoph Dorn]

There is no documentation for the new headers available yet. For now, please look at the FirePHPCore source files. You can just copy these headers:

X-Wf-Protocol-1 http://meta.wildfirehq.org/Protocol/JsonStream/0.2
X-Wf-1-Plugin-1 http://meta.firephp.org/Wildfire/Plugin/FirePHP/Library-FirePHPCore/0.2.0
X-Wf-1-Structure-1 http://meta.firephp.org/Wildfire/Structure/FirePHP/FirebugConsole/0.1

And then proceed with the logging messages:

X-Wf-1-1-1-1 30|[{"Type":"LOG"},"Hello World"]|
X-Wf-1-1-1-2 30|[{"Type":"LOG"},"Hello World"]|

The number before the "|" specifies the number of characters between the two "|". To split a message into several headers (if larger than 5,000 characters) use:

X-Wf-1-1-1-1 30|[{"Type":"LOG"},"Hell|\
X-Wf-1-1-1-2 |o Wo|\
X-Wf-1-1-1-2 |rld"]|

[smith]

X-Wf-1-1-1-1 30|[{"Type":"LOG"},"Hell|\
X-Wf-1-1-1-2 |o Wo|\
X-Wf-1-1-1-2 |rld"]|

Should the third "X-Wf..." here end with 3?

I tried this in my implementation with a very long (50000 char) string, and it only gave me the first and last chunks.

If I increment the index on every chunk, it should work in theory, but I'm still having problems. It could be platform specific (I'm using Jaxer.)

Any clarification would help.

Thanks,

Nathan

[Christoph Dorn]

X-Wf-1-1-1-1 30|[{"Type":"LOG"},"Hell|\
X-Wf-1-1-1-2 |o Wo|\
X-Wf-1-1-1-3 |rld"]|

Each message must have a unique key. I have tested the above and it works for me.

[smith]

Christoph,

Thanks for the clarification. I tried this on ASP and it worked. I think I've run into a strange bug in Jaxer, though.

Nathan