From cf58e37ad31e02b4431f407220982b86f08c244b Mon Sep 17 00:00:00 2001 From: MaPePeR Date: Tue, 30 May 2023 18:29:29 +0200 Subject: [PATCH] Remove obsolete TODO and make slow-down warning bold. --- docs/source/rabbitmq-tutorial/7-publisher-confirms.rst | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/source/rabbitmq-tutorial/7-publisher-confirms.rst b/docs/source/rabbitmq-tutorial/7-publisher-confirms.rst index 0e69798c..2b6b7212 100644 --- a/docs/source/rabbitmq-tutorial/7-publisher-confirms.rst +++ b/docs/source/rabbitmq-tutorial/7-publisher-confirms.rst @@ -76,15 +76,11 @@ The handling of the exception usually consists in logging an error message and/o Different client libraries have different ways to synchronously deal with publisher confirms, so make sure to read carefully the documentation of the client you are using. -This technique is very straightforward but also has a major drawback: it significantly slows down publishing, as the +This technique is very straightforward but also has a major drawback: it **significantly slows down publishing**, as the confirmation of a message blocks the publishing of all subsequent messages. This approach is not going to deliver throughput of more than a few hundreds of published messages per second. Nevertheless, this can be good enough for some applications. -.. - TODO: Do we need to specify, that wait_for cancels the awaitables waiting for publisher confirmation when the timeout - occurs? - Strategy #2: Publishing Messages in Batches +++++++++++++++++++++++++++++++++++++++++++