Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Cleaned up design file

  • Loading branch information...
commit 09404542f44472e05e9f789c9642e8c3da5e66f0 1 parent 4cd1a4d
Bart ten Brinke authored June 24, 2009

Showing 1 changed file with 6 additions and 8 deletions. Show diff stats Hide diff stats

  1. 14  DESIGN.rdoc
14  DESIGN.rdoc
Source Rendered
@@ -2,14 +2,13 @@
2 2
 RLA is set up like a simple pipe and filter system.
3 3
 
4 4
 This allows you to easily add extra reports, filters and outputs.
5  
-
6  
-1) Build pipeline.
7 5
                              -> Aggregator  (database)
8 6
   Source -> Filter -> Filter -> Aggregator  (summary report)  -> Output
9 7
                              -> Aggregator  (...)
10  
-                             
11  
-2) Start chunk producer and push chunks through pipeline.
12  
- Controller.start
  8
+
  9
+When the pipeline has been constructed, we Start chunk producer (source) and push requests through pipeline.
  10
+
  11
+  Controller.start
13 12
 
14 13
 === Source
15 14
 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
32 31
 generate a wide range of statistical reports from them.
33 32
 
34 33
 === Running the pipeline
35  
-3) Gather output from pipeline.
36  
-  Controller.report
37  
-
38 34
 All Aggregators are asked to report what they have done. For example the database will report: I stuffed x requests
39 35
 into SQLite database Y. The Summarizer will output its reports.
40 36
 
  37
+  Controller.report
  38
+
41 39
 The output is pushed to a RequestLogAnalyzer::Output object, which takes care of the output.
42 40
 It can generate either ASCII, UTF8 or even HTML output.
43 41
 

0 notes on commit 0940454

Please sign in to comment.
Something went wrong with that request. Please try again.