modules/trace/ROADMAP.txt

// $Id$

This is a listing of known bugs, features that mostly work but are still
somewhat in progress, features that are being considered or planned for
implementation, and just miscellaneous far-out ideas that could, in
principle, be implemented if one had the time and inclination to do so.

(NOTE: there is no guarantee any of these items will, in fact, be
implemented, nor should any possible scheduling indications be construed as
promises under any circumstances. TANSTAAFL. If you absolutely need
something implemented right now, please contact the developers to see if
they're available for contract work, or whether a modest donation could
perhaps speed things along.)

TODO: MISSING FEATURES
----------------------
* Tracing of watchdog messages has not yet been implemented.

TODO: NEAR-TERM TASKS
---------------------
* Filter by user role and/or by IP address?
* Add an option to overwrite the output file, instead of appending to it.
* Add two new output drivers: socket and email.
* Add an option to ignore repeated, duplicate errors.
* Test and ensure compatibility with the Devel module (especially with
  regards to the shared `dev_query' variable).
* Drupal core patch to improve tracing capabilities in the database layer.
* Write the developer documentation (API.txt).

TODO: UNDER CONSIDERATION
-------------------------
* Add host name to the REQUEST trace message (useful for multi-sites).
* Add option to include the contents of the page response into the trace
  output, or to write each response into a separate file in a directory?
* Look into adding XDebug support?
* Allow multiple output drivers to be active simultaneously, with possibly
  different settings. Useful for having critical production error messages
  go into the syslog or be e-mailed, while still having the possibility to
  send more verbose debugging output to a file from time to time.
* Add setting to add trace output as a comment to the end of the HTML page?
* More accurate time adjustments to account for time lost to tracing?

TODO: LONG-TERM IDEAS
---------------------
* Implement ability to dynamically and on-the-fly inject tracing statements
  into any third-party module with some fancy tokenizing hacks. (Requires
  early calls to drupal_get_filename() to override module filenames before
  they are loaded by Drupal.)
* Look into PHP's register_tick_function() for potential advanced uses.
1	// $Id$
2
3	This is a listing of known bugs, features that mostly work but are still
4	somewhat in progress, features that are being considered or planned for
5	implementation, and just miscellaneous far-out ideas that could, in
6	principle, be implemented if one had the time and inclination to do so.
7
8	(NOTE: there is no guarantee any of these items will, in fact, be
9	implemented, nor should any possible scheduling indications be construed as
10	promises under any circumstances. TANSTAAFL. If you absolutely need
11	something implemented right now, please contact the developers to see if
12	they're available for contract work, or whether a modest donation could
13	perhaps speed things along.)
14
15	TODO: MISSING FEATURES
16	----------------------
17	* Tracing of watchdog messages has not yet been implemented.
18
19	TODO: NEAR-TERM TASKS
20	---------------------
21	* Filter by user role and/or by IP address?
22	* Add an option to overwrite the output file, instead of appending to it.
23	* Add two new output drivers: socket and email.
24	* Add an option to ignore repeated, duplicate errors.
25	* Test and ensure compatibility with the Devel module (especially with
26	regards to the shared `dev_query' variable).
27	* Drupal core patch to improve tracing capabilities in the database layer.
28	* Write the developer documentation (API.txt).
29
30	TODO: UNDER CONSIDERATION
31	-------------------------
32	* Add host name to the REQUEST trace message (useful for multi-sites).
33	* Add option to include the contents of the page response into the trace
34	output, or to write each response into a separate file in a directory?
35	* Look into adding XDebug support?
36	* Allow multiple output drivers to be active simultaneously, with possibly
37	different settings. Useful for having critical production error messages
38	go into the syslog or be e-mailed, while still having the possibility to
39	send more verbose debugging output to a file from time to time.
40	* Add setting to add trace output as a comment to the end of the HTML page?
41	* More accurate time adjustments to account for time lost to tracing?
42
43	TODO: LONG-TERM IDEAS
44	---------------------
45	* Implement ability to dynamically and on-the-fly inject tracing statements
46	into any third-party module with some fancy tokenizing hacks. (Requires
47	early calls to drupal_get_filename() to override module filenames before
48	they are loaded by Drupal.)
49	* Look into PHP's register_tick_function() for potential advanced uses.