May 10, 2018 · Apr 7, 2019 · Apr 28, 2019 · Apr 28, 2019 · Apr 28, 2019 · Apr 28, 2019
diff --git a/components/messenger/transports.rst b/components/messenger/transports.rst
 "transports". Transports are responsible for routing messages to and from
 the message brokers.

 Every transport is configurable using a DSN. This DSN allows you tochose the
 Every transport is configurable using a DSN. This DSN allows you tochoose the
 transport layer as well as configure it.

 AMQP
 commonly implemented with RabbitMQ. The Messenger component has built-in
 support for AMQP.

 How itworks?
 HowDoesitWorks?
 ~~~~~~~~~~~~~

 A DSN that starts with ``amqp://`` is recognized and used to create
    By default, RabbitMQ uses ``guest`` as a username and ``guest`` as a password
    and has a ``/`` vhost.

 Errorhandling
 ErrorHandling
 ~~~~~~~~~~~~~~

 If something wrong happens (i.e. an exception is thrown) while handling your message,
 the defaultbehaviour is that your message will be "NACK" and requeued.
 the defaultbehavior is that your message will be "NACK" and requeued.

 However, if your exception implements the ``RejectMessageExceptionInterface`` interface,
 the message will be rejected from the queue.
 and can't really process some messages. To handle this scenario, there is a built-in
 retry mechanism that can be enabled via your DSN::

 .. code-block:: bash
    amqp://guest:guest@localhost/%2f/messages
      ?retry[attempts]=3
      &retry[ttl][0]=10000
 fails, the message will be moved to a "dead queue" and you will have to manually
 handle this message.

 DSNconfiguration reference
 DSNConfiguration Reference
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~

 The options available in the DSN are documented on the ``Connection`` class
 with brokers like Kafka, Google Pub/Sub, AWS SQS and more. Check out the transport
 documentation in `Enqueue's official repository`_.

 Your owntransport
 Your ownTransport
 ------------------

 If there is no available transport for your message broker, you can easily
 create your own.
 If there is no available transport for your message broker, you can create your own.

 Your ownsender
 Your ownSender
 ~~~~~~~~~~~~~~~

 Using the ``SenderInterface``, you caneasilycreate your own message sender.
 Let's say you already have an ``ImportantAction`` message going through the
 Using the ``SenderInterface``, you can create your own message sender.
 You already have an ``ImportantAction`` message going through the
 message bus and handled by a handler. Now, you also want to send this message as
 an email via your sender::

 .. code-block:: php

    // src/MessageSender/ImportantActionToEmailSender.php

    namespace App\MessageSender;

    use App\Message\ImportantAction;
 A receiver is responsible for receiving messages from a source and dispatching
 them to the application.

 Let's say you already processed some "orders" in your application using a
 You already processed some "orders" in your application using a
 ``NewOrder`` message. Now you want to integrate with a 3rd party or a legacy
 application but you can't use an API and need to use a shared CSV file with new
 orders.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -8,7 +8,7 @@ To send and receive messages via message brokers, the Messenger component has
		"transports". Transports are responsible for routing messages to and from
		the message brokers.

		Every transport is configurable using a DSN. This DSN allows you tochose the
		Every transport is configurable using a DSN. This DSN allows you tochoose the
		transport layer as well as configure it.

		AMQP
Expand All		@@ -18,7 +18,7 @@ The most famous message broker protocol is probably AMQP, which is most
		commonly implemented with RabbitMQ. The Messenger component has built-in
		support for AMQP.

		How itworks?
		HowDoesitWorks?
		~~~~~~~~~~~~~

		A DSN that starts with ``amqp://`` is recognized and used to create
Expand All		@@ -34,11 +34,11 @@ queue on the ``/`` vhost (the ``%2f`` is a url-encoded ``/``).
		By default, RabbitMQ uses ``guest`` as a username and ``guest`` as a password
		and has a ``/`` vhost.

		Errorhandling
		ErrorHandling
		~~~~~~~~~~~~~~

		If something wrong happens (i.e. an exception is thrown) while handling your message,
		the defaultbehaviour is that your message will be "NACK" and requeued.
		the defaultbehavior is that your message will be "NACK" and requeued.

		However, if your exception implements the ``RejectMessageExceptionInterface`` interface,
		the message will be rejected from the queue.
Expand All		@@ -51,6 +51,7 @@ arise. Typically, a 3rd party provider is down or your system is under heavy loa
		and can't really process some messages. To handle this scenario, there is a built-in
		retry mechanism that can be enabled via your DSN::

		.. code-block:: bash
		amqp://guest:guest@localhost/%2f/messages
llaakkkk marked this conversation as resolved. Show resolvedHide resolved
		?retry[attempts]=3
		&retry[ttl][0]=10000
Expand All		@@ -63,7 +64,7 @@ it will wait 30 seconds. After the 3rd failure, it will wait a minute. If it sti
		fails, the message will be moved to a "dead queue" and you will have to manually
		handle this message.

		DSNconfiguration reference
		DSNConfiguration Reference
		~~~~~~~~~~~~~~~~~~~~~~~~~~~

		The options available in the DSN are documented on the ``Connection`` class
Expand All		@@ -76,20 +77,23 @@ Probably one of the most famous PHP queue-broker libraries, Enqueue, has 10+ ada
		with brokers like Kafka, Google Pub/Sub, AWS SQS and more. Check out the transport
		documentation in `Enqueue's official repository`_.

		Your owntransport
		Your ownTransport
		------------------

		If there is no available transport for your message broker, you can easily
		create your own.
		If there is no available transport for your message broker, you can create your own.

		Your ownsender
		Your ownSender
		~~~~~~~~~~~~~~~

		Using the ``SenderInterface``, you caneasilycreate your own message sender.
		Let's say you already have an ``ImportantAction`` message going through the
		Using the ``SenderInterface``, you can create your own message sender.
		You already have an ``ImportantAction`` message going through the
		message bus and handled by a handler. Now, you also want to send this message as
		an email via your sender::

		.. code-block:: php

		// src/MessageSender/ImportantActionToEmailSender.php

		namespace App\MessageSender;
llaakkkk marked this conversation as resolved. Show resolvedHide resolved

		use App\Message\ImportantAction;
Expand DownExpand Up		@@ -129,7 +133,7 @@ Your own receiver
		A receiver is responsible for receiving messages from a source and dispatching
		them to the application.

		Let's say you already processed some "orders" in your application using a
		You already processed some "orders" in your application using a
		``NewOrder`` message. Now you want to integrate with a 3rd party or a legacy
		application but you can't use an API and need to use a shared CSV file with new
		orders.
Expand Down