Skip to content
This repository
Browse code

typo on README.md

  • Loading branch information...
commit c84ff0ec842bcf8b6bf192f82884ea7d2cafe898 1 parent ef478f1
Francisco Javier Palma authored September 28, 2012

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

  1. 8  README.md
8  README.md
Source Rendered
@@ -93,7 +93,7 @@ Configure the `rabbitmq` service in your config:
93 93
                 callback:         upload_picture_service
94 94
         ...
95 95
 
96  
-Here we configure the connection service and the message endpoints that our application will have. In this example your service container will contain the service `rabbitmq.upload_picture_producer` and `rabbitmq.upload_picture_consumer`. The later expects that there's a service called `upload_picture_service`.
  96
+Here we configure the connection service and the message endpoints that our application will have. In this example your service container will contain the service `old_sound_rabbit_mq.upload_picture_producer` and `old_sound_rabbit_mq.upload_picture_consumer`. The later expects that there's a service called `upload_picture_service`.
97 97
 
98 98
 If you don't specify a connection for the client, the client will look for a connection with the same alias. So for our `upload_picture` the service container will look for an `upload_picture` connection.
99 99
 
@@ -121,7 +121,7 @@ Now let's say that you want to process picture uploads in the background. After
121 121
         ...
122 122
     }
123 123
 
124  
-As you can see, if in your configuration you have a producer called __upload\_picture__, then in the service container you will have a service called __rabbitmq.upload\_picture\_producer__.
  124
+As you can see, if in your configuration you have a producer called __upload\_picture__, then in the service container you will have a service called __old_sound_rabbit_mq.upload\_picture\_producer__.
125 125
 
126 126
 The next piece of the puzzle is to have a consumer that will take the message out of the queue and process it accordingly.
127 127
 
@@ -230,7 +230,7 @@ And then add the following code to our controller:
230 230
         ...
231 231
     }
232 232
 
233  
-As you can see there, if our client id is __integer\_store__, then the service name will be __rabbitmq.integer\_store_rpc__. Once we get that object we place a request on the server by calling `addRequest` that expects three parameters:
  233
+As you can see there, if our client id is __integer\_store__, then the service name will be __old_sound_rabbit_mq.integer\_store_rpc__. Once we get that object we place a request on the server by calling `addRequest` that expects three parameters:
234 234
 
235 235
 - The arguments to be sent to the remote procedure call.
236 236
 - The name of the RPC server, in our case __random\_int__.
@@ -288,7 +288,7 @@ When we start an Anonymous Consumer, it will take care of such details and we ju
288 288
 
289 289
 Now, how to configure and run such consumer?
290 290
 
291  
-    rabbitmq.config:
  291
+    old_sound_rabbit_mq.config:
292 292
         ...
293 293
         anon_consumers:
294 294
             logs_watcher:

0 notes on commit c84ff0e

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