)]}'
{"doc/source/rpc.rst":[{"author":{"_account_id":16237,"name":"venkatamahesh","email":"venkatamaheshkotha@gmail.com","username":"venkatamahesh"},"change_message_id":"b6f2f331f5d1fcc82e09a677cda885d0bddaf365","unresolved":false,"context_lines":[{"line_number":137,"context_line":"    * Auto_delete: if set, the exchange is deleted when all queues have finished using it. Default is False."},{"line_number":138,"context_line":"    * Exclusive: exclusive queues (such as non-shared) may only be consumed from by the current connection. When exclusive is on, this also implies auto_delete. Default is False."},{"line_number":139,"context_line":"    * Exchange_type: AMQP defines several default exchange types (routing algorithms) that covers most of the common messaging use cases."},{"line_number":140,"context_line":"    * Auto_ack: acknowledgement is handled automatically once messages are received. By default auto_ack is set to False, and the receiver is required to manually handle acknowledgment."},{"line_number":141,"context_line":"    * No_ack: it disable acknowledgement on the server-side. This is different from auto_ack in that acknowledgement is turned off altogether. This functionality increases performance but at the cost of reliability. Messages can get lost if a client dies before it can deliver them to the application."},{"line_number":142,"context_line":"    * 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."},{"line_number":143,"context_line":"      Publishers specify most the parameters of Consumers (such as they do not specify a queue name), but they can also specify the following:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a1a9d01_d602756f","side":"PARENT","line":140,"updated":"2015-09-24 16:44:22.000000000","message":"this is correct spell","commit_id":"2dae8b4c8710cd8a3a327be042669cbf0e881b5d"},{"author":{"_account_id":16237,"name":"venkatamahesh","email":"venkatamaheshkotha@gmail.com","username":"venkatamahesh"},"change_message_id":"b6f2f331f5d1fcc82e09a677cda885d0bddaf365","unresolved":false,"context_lines":[{"line_number":138,"context_line":"    * Exclusive: exclusive queues (such as non-shared) may only be consumed from by the current connection. When exclusive is on, this also implies auto_delete. Default is False."},{"line_number":139,"context_line":"    * Exchange_type: AMQP defines several default exchange types (routing algorithms) that covers most of the common messaging use cases."},{"line_number":140,"context_line":"    * Auto_ack: acknowledgement is handled automatically once messages are received. By default auto_ack is set to False, and the receiver is required to manually handle acknowledgment."},{"line_number":141,"context_line":"    * No_ack: it disable acknowledgement on the server-side. This is different from auto_ack in that acknowledgement is turned off altogether. This functionality increases performance but at the cost of reliability. Messages can get lost if a client dies before it can deliver them to the application."},{"line_number":142,"context_line":"    * 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."},{"line_number":143,"context_line":"      Publishers specify most the parameters of Consumers (such as they do not specify a queue name), but they can also specify the following:"},{"line_number":144,"context_line":"    * Delivery_mode: the default delivery mode used for messages. The value is an integer. The following delivery modes are supported by RabbitMQ:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a1a9d01_362091f7","side":"PARENT","line":141,"updated":"2015-09-24 16:44:22.000000000","message":"Undo the change, the spell is correct","commit_id":"2dae8b4c8710cd8a3a327be042669cbf0e881b5d"},{"author":{"_account_id":16237,"name":"venkatamahesh","email":"venkatamaheshkotha@gmail.com","username":"venkatamahesh"},"change_message_id":"b6f2f331f5d1fcc82e09a677cda885d0bddaf365","unresolved":false,"context_lines":[{"line_number":137,"context_line":"    * Auto_delete: if set, the exchange is deleted when all queues have finished using it. Default is False."},{"line_number":138,"context_line":"    * Exclusive: exclusive queues (such as non-shared) may only be consumed from by the current connection. When exclusive is on, this also implies auto_delete. Default is False."},{"line_number":139,"context_line":"    * Exchange_type: AMQP defines several default exchange types (routing algorithms) that covers most of the common messaging use cases."},{"line_number":140,"context_line":"    * Auto_ack: acknowledgment is handled automatically once messages are received. By default auto_ack is set to False, and the receiver is required to manually handle acknowledgment."},{"line_number":141,"context_line":"    * No_ack: it disable acknowledgment on the server-side. This is different from auto_ack in that acknowledgment is turned off altogether. This functionality increases performance but at the cost of reliability. Messages can get lost if a client dies before it can deliver them to the application."},{"line_number":142,"context_line":"    * 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."},{"line_number":143,"context_line":"      Publishers specify most the parameters of Consumers (such as they do not specify a queue name), but they can also specify the following:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a1a9d01_564665c0","line":140,"updated":"2015-09-24 16:44:22.000000000","message":"At the end : acknowledgment \u003d\u003e acknowledgement","commit_id":"b2f15f6d5138fab56959a6a2f318de18df5daa28"}]}