Skip to content

[Messenger] Transport not mandatory #10092

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 19, 2018
Merged

[Messenger] Transport not mandatory #10092

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bdbe542
Transport not mandatory
kunicmarko20 Jul 18, 2018
f0942d2
Reword
javiereguiluz Jul 19, 2018
47e275b
Reword
javiereguiluz Jul 19, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions messenger.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,9 +100,11 @@ Once you've created your handler, you need to register it:
Transports
----------

The communication with queuing systems or third parties is delegated to
libraries for now. The built-in AMQP transport allows you to communicate with
most of the AMQP brokers such as RabbitMQ.
By default, messages are processed as soon as they are dispatched. If you prefer
to process messages asynchronously, you must configure a transport. These
transports communicate your application with queuing systems or third parties.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more. 

- communicate your application with queuing systems
+ communicate with your application via queuing systems

The built-in AMQP transport allows you to communicate with most of the AMQP
brokers such as RabbitMQ.

.. note::

Expand Down