Where code meets community
ALPHA

FirePHP 1.0 uses Insight to collect application internal data and Wildfire to send this data to the client without interfering with the application. Both these projects are open source and intended to be ported to many programming languages.

More documentation on Wildfire will be available in time.

FirePHP uses a different wildfire mode to transfer data based on the configuration approach used:

  1. If the Traditional: FirePHPCore approach is used ALL data is sent in the response headers.
  2. If the Configure: constants or Configure: files approach is used only a small pointer is sent in the response headers and the client makes a secondary request to fetch the data. See Concepts for more information.

Wildfire Implementations

Official:

Java, Perl, Ruby and other language implementations are planned.

Third party:

All data in headers (1)

Only a limited amount of data can be sent in the response headers before it may get trimmed in transport to the client. This is a limitation of sending data in the response headers. If more data needs to be sent see Secondary Request (2).

Any application can send log messages in the response headers and the FirePHP client will route these to the Firebug Console.

A simple Hello World message (response 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.0.0master1106021548
X-Wf-1-Structure-1: http://meta.firephp.org/Wildfire/Structure/FirePHP/FirebugConsole/0.1
X-Wf-1-1-1-1: 63|[{"Type":"LOG","File":"/path/to/file","Line":10},"Hello World"]|
X-Wf-1-Index: 1

For more information see http://www.firephp.org/Wiki/Reference/Protocol

A bunch of examples can be found here: http://reference.developercompanion.com/Tools/FirePHPCompanion/Run/Examples/TestRunner/

Secondary Request (2)

Large amounts of data can be sent using this approach.

Any application can send a pointer message in the response headers and serve the log messages to the corresponding secondary client request. Depending on how the wildfire messages are addressed the client will direct them to the appropriate target.

A bunch of examples can be found here: http://reference.developercompanion.com/Tools/FirePHPCompanion/Run/Examples/TestRunner/

More documentation on the format of these messages will be available in time.

A simple pointer message (response headers):

x-request-id: 1309470322490165
x-wf-protocol-1: http://registry.pinf.org/cadorn.org/wildfire/@meta/protocol/component/0.1.0
x-wf-1-1-receiver: http://registry.pinf.org/cadorn.org/wildfire/@meta/receiver/transport/0
x-wf-1-1-1-sender: http://registry.pinf.org/cadorn.org/wildfire/packages/lib-php/lib/Wildfire/Transport.php
x-wf-1-1-1-1: 119||{"url":"http://example.com/","headers":{"x-insight":"transport"},"payload":{"key":"3a5d6bac25c2ed871e7344063fb5d183"}}|
x-wf-1-index: 1

The x-request-id header should be set to the same value as the corresponding header in the request.

Given the pointer message above, the client will make a call to:

POST / HTTP/1.1
Host: example.com
x-insight: transport

payload=%7B%22key%22%3A%223a5d6bac25c2ed871e7344063fb5d183%22%7D

payload = encodeURIComponent(JSON.stringify({key: "3a5d6bac25c2ed871e7344063fb5d183"}))

The client expects a wildfire payload in the response body:

x-wf-protocol-1: http://registry.pinf.org/cadorn.org/wildfire/@meta/protocol/component/0.1.0
x-wf-1-1-receiver: http://registry.pinf.org/cadorn.org/insight/@meta/receiver/console/page/0
x-wf-1-1-1-sender: http://registry.pinf.org/cadorn.org/github/firephp-libs/programs/standalone/examples/TestRunner/?lib=cadorn.org/github/firephp-libs/packages/insight@0.0.0master1106021548
x-wf-1-1-1-1: 217|{"context":"page","target":"console","file":"/path/to/file","line":11,"lang.id":"registry.pinf.org/cadorn.org/github/renderers/packages/php/master"}|{"origin":{"type":"text","text":"Hello World","lang.type":"string"}}|
x-wf-1-index: 1

Homepage: Sourcemint.com

Status

Sourcemint is incomplete ALPHA technology and continuously evolving in sync with underlying and related projects. Production ready aspects will be documented and made available in time. Your Feedback is welcome and appreciated!

Who

Sourcemint is one of the results of intense focus by Christoph Dorn over the past several years and continuous exploration throughout Christoph's interest in software development over the past 15+ years.

Sourcemint is the love child of one person guided by the voices of passionate developers at the top of their game who are leading the industry into a new era of software development.

What

Sourcemint is an integral part of Christoph's work intended to realize his dream of one global toolchain under which components may be arbitrarily combined into maintainable mission critical systems by providing an all-encompassing and organized package repository from which consistent and autonomic systems may be built.

Sourcemint provides an automated software building and integration service as well as an intelligent software delivery network to distribute built software to all deployed systems and Internet users.

This means an arbitrary (code, configuration, network, ...) change may be made to a software system which can then be automatically built, tested, distributed and deployed. Every change constitutes a completely new system made possible by the fact that changes, any changes, are cheap and fully tested in every way before going live.

Just imagine what this means in your daily work.

Why

Automated software builds, continuous integration processes, streamlined issue trackers, community supported software, source control, online collaboration and automated cloud deployment have wet our appetite but hardly scratch the surface of what it actually means to have a completely automated production cycle from idea to delivery. The full potential is only realized once these separate solutions addressing different areas work together harmoniously.

What has been missing is new ways of looking at how to build software.

How

Christoph's work provides a new way to build software that is not necessarily new in the sense of ideas or technology but rather arrangement and timing. Christoph has through exploration and experimentation distilled current cutting edge technology, knowledge and wisdom into a toolchain platform called PINF available open source under the MIT license to realize a new breed of software.

Imagine software and systems that just work and are a pleasure to maintain.

Sourcemint is built entirely on PINF, as is all of Christoph's work, and can be used by any developer to tap into the power of the PINF approach to build open source or commercial libraries, frameworks, applications, systems and services.

Christoph's hope is that PINF and related projects will provide a foundation for developers to cooperate more widely and experiment with new ideas by eliminating some of the major constraints imposed by traditional toolchains. Traditional toolchains create systems that typically rot because they are practically impossible to refactor. We need a toolchain such as PINF which has refactorability designed into its core.

Let's create software that breathes with life and is in large part self-sustaining!

You

Join Christoph in his mission to help you, the developer, and help yourself by broadly applying the tools and approaches you know work to all of your work. Lean on PINF, your mind is begging you. Learn it, teach others, and let your inspiration soar!

Follow Sourcemint and PINF on twitter to watch for news of cutting-edge tools, tutorials and services coming online. You can also follow Christoph's work directly.