From 029218df5b7fbd6a7e4f945ecd32f84236885f53 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Wed, 22 Apr 2009 08:38:25 +0200 Subject: another typo fix... --- doc/queues_analogy.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/queues_analogy.html b/doc/queues_analogy.html index e82f9d15..d7533ad5 100644 --- a/doc/queues_analogy.html +++ b/doc/queues_analogy.html @@ -59,7 +59,7 @@ actively initiate reception of a message in the same way a TV set cannot activel "initiate" a TV show - both can only "handle" (display or process) what is sent to them.

Now let's look at the action queues: here, the active part, the producer, is the -Parser and Filter Engine. The passive part is the Action Processor. The latter does any +Parser and Filter Engine. The passive part is the Action Processor. The later does any processing that is necessary to call the output plugin, in particular it processes the template to create the plugin calling parameters (either a string or vector of arguments). From the action queue's point of view, Action Processor and Output form a single entity. Again, the -- cgit