diff --git a/module001-ch008-queues-messaging.xml b/module001-ch008-queues-messaging.xml index e03f58fb..c1a25816 100644 --- a/module001-ch008-queues-messaging.xml +++ b/module001-ch008-queues-messaging.xml @@ -51,7 +51,7 @@ Nova implements RPC (both request+response, and one-way, respectively nicknamed ‘rpc.call’ and ‘rpc.cast’) over AMQP by providing an adapter class which take cares of marshaling and - un-marshalling of messages into function calls. Each Nova service, + un-marshaling of messages into function calls. Each Nova service, such as Compute, Scheduler, and so on, creates two queues at the initialization time, one which accepts messages with routing keys ‘NODE-TYPE.NODE-ID’, for example, compute.hostname, and another, @@ -155,24 +155,24 @@ operation: - a Topic Publisher is instantiated to send the message + A Topic Publisher is instantiated to send the message request to the queuing system; immediately before the - publishing operation, a Direct Consumer is instantiated to + publishing operation. A Direct Consumer is instantiated to wait for the response message. - once the message is dispatched by the exchange, it is + Once the message is dispatched by the exchange, it is fetched by the Topic Consumer dictated by the routing key (such as ‘topic.host’) and passed to the Worker in charge of the task. - once the task is completed, a Direct Publisher is + Once the task is completed, a Direct Publisher is allocated to send the response message to the queuing system. - once the message is dispatched by the exchange, it is + Once the message is dispatched by the exchange, it is fetched by the Direct Consumer dictated by the routing key (such as ‘msg_id’) and passed to the Invoker. @@ -210,7 +210,7 @@ AMQP Broker Load At any given time the load of a message broker node running - either Qpid or RabbitMQ is function of the following + either Qpid or RabbitMQ is a function of the following parameters: @@ -248,19 +248,19 @@ - compute.phantom (phantom is hostname) + compute.phantom (phantom is the hostname) compute - network.phantom (phantom is hostname) + network.phantom (phantom is the hostname) network - scheduler.phantom (phantom is hostname) + scheduler.phantom (phantom is the hostname) scheduler @@ -274,7 +274,7 @@ order to instantiate a Connection object that connects to the RabbitMQ server (please note that most of the following material can be also found in the Kombu documentation; it has been - summarized and revised here for sake of clarity): + summarized and revised here for the sake of clarity): Hostname: The hostname to @@ -318,7 +318,7 @@ to the server. The default is False. - More precisely Consumers need the following parameters: + More precisely consumers need the following parameters: Connection: the above @@ -407,8 +407,8 @@ Auto_declare:if this is True and the exchange name is set, the exchange will be automatically declared at instantiation. Auto declare is on by - default. Publishers specify most the parameters of Consumers - (such as they do not specify a queue name), but they can also + default. Publishers specify most the parameters of consumers + (they do not specify a queue name), but they can also specify the following: