RabbitMQReceiver v0.1.5 RabbitMQReceiver
Documentation for RabbitMQReceiver.
Link to this section Summary
Functions
Hello world
Starts linked RabbitMQReceive rprocess and returns standard {:ok, pid}, or raises otherwise. Note that a callback_moddule.callback_function now accepts a %ReceiverMessage{} struct instead of tuples. option_switches - is intended for passing options determining various integration types and the way the queue and exchanges and stuff is configured. Now, supported options are: :exchange - which indicated that the queue has a configured exchange (not a default one). :exchange_type - denotes the type of the Exchange. Supported values include: :direct, :fanout, :topic, :match (and :headers). :binding_keys - a list of values denoting topics bound to the queue. Option switches should be provided either as a keyword lists (where value is required according to the meaning) or as options (just atoms in the list)
Link to this section Functions
Hello world.
Examples
iex> RabbitMQReceiver.hello
:world
Starts linked RabbitMQReceive rprocess and returns standard {:ok, pid}, or raises otherwise. Note that a callback_moddule.callback_function now accepts a %ReceiverMessage{} struct instead of tuples. option_switches - is intended for passing options determining various integration types and the way the queue and exchanges and stuff is configured. Now, supported options are: :exchange - which indicated that the queue has a configured exchange (not a default one). :exchange_type - denotes the type of the Exchange. Supported values include: :direct, :fanout, :topic, :match (and :headers). :binding_keys - a list of values denoting topics bound to the queue. Option switches should be provided either as a keyword lists (where value is required according to the meaning) or as options (just atoms in the list).