@@ -2,14 +2,13 @@ RLA is set up like a simple pipe and filter system. This allows you to easily add extra reports, filters and outputs. - -1) Build pipeline. -> Aggregator (database) Source -> Filter -> Filter -> Aggregator (summary report) -> Output -> Aggregator (...) - -2) Start chunk producer and push chunks through pipeline. - Controller.start + +When the pipeline has been constructed, we Start chunk producer (source) and push requests through pipeline. + + Controller.start === Source RequestLogAnalyzer::Source is an Object that pushes requests into the chain. @@ -32,12 +31,11 @@ For example: the Database aggregator will just store all the requests into a SQL generate a wide range of statistical reports from them. === Running the pipeline -3) Gather output from pipeline. - Controller.report - All Aggregators are asked to report what they have done. For example the database will report: I stuffed x requests into SQLite database Y. The Summarizer will output its reports. + Controller.report + The output is pushed to a RequestLogAnalyzer::Output object, which takes care of the output. It can generate either ASCII, UTF8 or even HTML output. DESIGN.rdoc 4cd1a4d3ff0ce1e180cc9ddc232cf2ccc874b3de Bart ten Brinke info@retrosync.com http://github.com/wvanbergen/request-log-analyzer/commit/09404542f44472e05e9f789c9642e8c3da5e66f0 09404542f44472e05e9f789c9642e8c3da5e66f0

2009-06-24T10:52:06-07:00

Cleaned up design file 8dda30110853c8d770b2e0275bcf1390b0604f3c Bart ten Brinke info@retrosync.com