Bus

The bus is used to dispatch messages. MessageBus'behavior is in its ordered

The bus is used to dispatch messages. MessageBus'behaviour is in its ordered

middleware stack. When using the message bus with Symfony's FrameworkBundle, the

following middlewares are configured for you:

#.``LoggingMiddleware`` (logs the processing of your messages)

#.``SendMessageMiddleware`` (enables asynchronous processing)

#.``HandleMessageMiddleware`` (calls the registered handle)

#.:code:`LoggingMiddleware` (logs the processing of your messages)

#.:code:`SendMessageMiddleware` (enables asynchronous processing)

#.:code:`HandleMessageMiddleware` (calls the registered handle)

Example::

Your adapter factory

TODO.

Same bus received and sender

The communication with queuing system or third parties is delegated to

libraries for now. The`built-in AMQP adapter`_ allows you to communicate with

libraries for now. The built-in AMQP adapter allows you to communicate with

most of the AMQP brokers such as RabbitMQ.

..note::

The first argument is the receiver's service name. It might have been created by

your:code:`adapaters` configuration or it can be your own receiver.

your:code:`adapters` configuration or it can be your own receiver.

Your own Adapters

Learn how to build your own adapters within the Component's documentation. Once

you have built your classes, you can register your adapater to be able to use

it via a DSN in the Symfony application.

you have built your classes, you can register your adapter factory to be able to

use it via a DSN in the Symfony application.

Register your factory