Saturday 19 July 2008This is nearly 15 years old. Be careful.

FirePHP is an intriguing Firebug plug-in: it uses a server-side library to send debugging information in response headers, which are extracted and nicely displayed in the browser.

One of the complexities of developing web applications is that your server is busy with lots of stuff at once. Load a single page, and there could be dozens of requests, once all the scripts, styles, images, and Ajax calls are through. If you have some debugging traces in the main page, they’ll get buried in all the other noise created by the subsequent requests.

FirePHP look like it gives a nice compartmentalization: the log messages from the main request stay tidy in Firebug. I haven’t used it yet, because I need to whipe up some Python server-side code (the name FirePHP doesn’t limit it to PHP debugging).


Paste and some other WSGI tools do this in middleware without the need for an extension, e.g., paste.debug.profile puts profiling information at the bottom of a page. paste.debug.prints just captures all (per-request) print statements and puts them in the page.
Still, Ian, if you're debugging code that is generating things like XML files, you really don't have any choice (I mean, I guess you could hack around it with comments or something, but that sucks). Still, it lets you be nicely output format agnostic.

Disclaimer, I don't actually use FirePHP. I've just heard about it and think its cool. :-)
I would love to list your python library on the FirePHP site should you go ahead with writing one.

Add a comment:

Ignore this:
Leave this empty:
Name is required. Either email or web are required. Email won't be displayed and I won't spam you. Your web site won't be indexed by search engines.
Don't put anything here:
Leave this empty:
Comment text is Markdown.