Broker implements a high level interface that can provide Consumer or Publisher

Config is passed into New when creating a Relay to tune various parameters around broker interactions.

Consumer is used to consume messages from a queue

Consumer is a type that is used only for consuming messages from a single queue. Multiple Consumers can multiplex a single relay

GOBSerializer implements the Serializer interface and uses the GOB format

InmemBroker implements the Broker interface in-memory

InmemConsumer implements the Consumer interface

InmemConsumer implements the Publisher interface

JSONSerializer implements the Serializer interface and uses JSON

PriorityQueue is a simple wrapper around a relay.Broker to manage a set of queues with varying priority.

Publisher is used to push messages into a queue

Publisher is a type that is used only for publishing messages to a single queue. Multiple Publishers can multiplex a single relay

Serializer interface is used to encode and decode messages. If not provided, a default serializer using gob is provided.

priorityResp is used as a container for response data during a Consume(). Since the response must be fed down a channel and contains multiple values,

retryBroker implements a resilient AMQP broker which automatically replaces the underlying channel if an unexpected error is observed. Due to AMQP's p

retryConsumer tracks the relay broker and an associated consumer, allowing the consumer to be replaced transparently in the face of failure.

retryPublisher wraps a relay broker and an associated publisher, allowing the underlying publisher's channel to be automatically swapped out if any er