ReactorDelivery
in
One message off the reactor's own queue (CONTRACT.md §22.1).
Table of Contents
Methods
- ack() : void
- Acknowledges the delivery.
- body() : string
- The raw message bytes, exactly as received.
- correlationId() : string
- The delivery's AMQP `correlation_id` basic property, echoed onto the reply publication. Not the authenticated binding either — the one in the signed body is.
- nack() : void
- Negatively acknowledges the delivery WITHOUT requeue.
- replyTo() : string
- The reply queue named in the delivery's AMQP `reply_to` basic property — standard AMQP RPC.
Methods
ack()
Acknowledges the delivery.
public
ack() : void
body()
The raw message bytes, exactly as received.
public
body() : string
Return values
stringcorrelationId()
The delivery's AMQP `correlation_id` basic property, echoed onto the reply publication. Not the authenticated binding either — the one in the signed body is.
public
correlationId() : string
Return values
stringnack()
Negatively acknowledges the delivery WITHOUT requeue.
public
nack() : void
There is no requeue parameter on purpose. A reactor's dispatch window is at most five seconds (§22.8), so a redelivered event can only ever produce a reply the server has already stopped reading — requeuing spends the broker's effort to guarantee a late answer.
replyTo()
The reply queue named in the delivery's AMQP `reply_to` basic property — standard AMQP RPC.
public
replyTo() : string
What the SERVER authenticates is not this property but the
correlation_id INSIDE the signed reply body (§22.1); this only says where
to put it.