Finished delayed message section documentation.

Author: Anton Vorontsov

RabbitMQ.Client.Core.DependencyInjection.sln

@@ -26,11 +26,11 @@ EndProject
 Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "docs", "docs", "{BC4CDBDE-4AEE-44B3-B00B-380EB1AC5E62}"
 ProjectSection(SolutionItems) = preProject
 	docs\changelog.md = docs\changelog.md
-	docs\documentation.md = docs\documentation.md
 	docs\rabbit-configuration.md = docs\rabbit-configuration.md
 	docs\exchange-configuration.md = docs\exchange-configuration.md
 	docs\message-production.md = docs\message-production.md
 	docs\message-consumption.md = docs\message-consumption.md
+	docs\readme.md = docs\readme.md
 EndProjectSection
 EndProject
 Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "images", "images", "{93D59B0E-856C-4260-B50E-57FE5C0F5073}"

docs/message-consumption.md

@@ -286,4 +286,7 @@ So you can use async/await power inside your message handler.
 
 ### Workflow of message handling
 
+
+
+
 For message production features see the [Previous page](message-production.md)

docs/message-production.md

@@ -107,8 +107,24 @@ await queueService.SendAsync(bytes, properties, exchangeName: "exchange.name", r
 ```
 
 ### Mechanism of sending delayed messages
-
+The implementation of sending deferred (delayed) messages in this project is quite tricky.
+The image below shows a model of the whole process of passing the message from the producer to the consumer.
 ![Model of sending delayed messages](./images/delayed-message-model.png)
 
+**Prerequisites.** Let's say that producer want to send a message to the exchange **"Exchange B"** with a routing key **"routing.key"** and delay in **30 seconds**.
+ -  Message goes to the exchange **"Exchange A"** whose responsibility is to manage delaying (storing) the message.
+ - After that a queue with a compound name and special arguments is being created. Name consists of three parts: routing key of sent message, word "delayed" and number of seconds delay.
+Queue arguments are as follows.
+```
+x-dead-letter-exchange : Exchange В
+x-dead-letter-routing-key : routing.key
+x-message-ttl : secondsDelay * 1000
+x-expires : secondsDelay * 1000 + 60000
+```
+ - A message, which gets in that queue, will have a specified ttl (time to live) and an exchange to which the message will be sent after expiration.
+ - That new queue bounds to the **Exchange A**. That queue will be automatically deleted if there are no more messages in it within a minute.
+ - Message goes to that queue, waits until expiration and goes in the **"Exchange B"**, which routes it as it should be.
+ - Message gets in the destination queue and consumer can retrieve that message.
+
 For the exchange configuration see the [Previous page](exchange-configuration.md) <br>
 For message consumption features see the [Next page](message-consumption.md)

docs/documentation.md docs/readme.mddocs/documentation.md renamed to docs/readme.md

@@ -7,7 +7,7 @@ This repository contains the library that provides functionality for wrapping [R
 
 ## Usage
 
-This section contains only example of basic usage of the library. You can find the [detailed documentation](./docs/documentation.md) in the docs directory where all functionality fully covered.
+This section contains only example of basic usage of the library. You can find the [detailed documentation](./docs/index.md) in the docs directory where all functionality fully covered.
 
 ### Producer