Zend_Wildfire.xml 1.6 KB

1234567891011121314151617181920212223242526272829303132333435363738
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!-- Reviewed: no -->
  3. <sect1 id="zend.wildfire.chapter">
  4. <title>Zend_Wildfire</title>
  5. <para>
  6. <classname>Zend_Wildfire</classname> is a component that facilitates communication
  7. between PHP code and
  8. <ulink url="http://www.wildfirehq.org/">Wildfire</ulink> client components.
  9. </para>
  10. <para>
  11. The purpose of the Wildfire Project is to develop standardized communication
  12. channels between a large variety of components and a dynamic and scriptable
  13. plugin architecture. At this time the primary
  14. focus is to provide a system to allow server-side PHP code to inject logging
  15. messages into the <ulink url="http://www.getfirebug.com/">Firebug</ulink>
  16. <ulink url="http://getfirebug.com/logging.html">Console</ulink>.
  17. </para>
  18. <para>
  19. For the purpose of logging to Firebug the
  20. <link linkend="zend.log.writers.firebug"><classname>Zend_Log_Writer_Firebug</classname></link>
  21. component is provided and a communication protocol has been developed
  22. that uses HTTP request and response headers to send data between the server and
  23. client components. It is great for logging intelligence data, generated during script
  24. execution, to the browser without interfering with the page content. Debugging
  25. AJAX requests that require clean JSON and XML responses is possible with this approach.
  26. </para>
  27. <para>
  28. There is also a <link linkend="zend.db.profiler.profilers.firebug">
  29. <classname>Zend_Db_Profiler_Firebug</classname></link> component to log database profiling
  30. information to Firebug.
  31. </para>
  32. </sect1>
  33. <!--
  34. vim:se ts=4 sw=4 et:
  35. -->