Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Add missing properties for exchange.publish

There are some properties used for exchange.publish but not listed in the doc (like userId, appId. etc..). These are written here: http://www.rabbitmq.com/resources/specs/amqp0-9-1.pdf under 1.8.1. Property and Method Summary, page 42. Node-ampq accept these as key-value for the options object. I

t's already supported by node-amp but now written in the docs. This commit just add those missing information.
  • Loading branch information...
commit 674202a9bd6b9bcdbe2b81c868b96dc2dbd6fcd7 1 parent 02d6ef1
@fatih fatih authored
Showing with 9 additions and 2 deletions.
  1. +7 −0 README.md
  2. +2 −2 amqp.js
View
7 README.md
@@ -369,7 +369,14 @@ is converted to JSON.
- `headers`: default `{}`. Arbitrary application-specific message headers.
- `deliveryMode`: Non-persistent (1) or persistent (2)
- `priority`: The message priority, 0 to 9.
+- `correlationId`: default null. Application correlation identifier
- `replyTo`: Usually used to name a reply queue for a request message.
+- `expiration`: default null. Message expiration specification
+- `messageId`: default null. Application message identifier
+- `timestamp`: default null. Message timestamp
+- `type`: default null. Message type name
+- `userId`: default null. Creating user id
+- `appId`: default null. Creating application id
`callback` is a function that will get called if the exchange is in confirm mode,
the value sent will be true or false, this is the presense of a error so true, means
View
4 amqp.js
@@ -1250,7 +1250,7 @@ Connection.prototype._sendMethod = function (channel, method, args) {
// - priority (0-9)
// - correlationId
// - replyTo
-// - experation
+// - expiration
// - messageId
// - timestamp
// - userId
@@ -2206,7 +2206,7 @@ Exchange.prototype._onMethod = function (channel, method, args) {
// - priority (0-9)
// - correlationId
// - replyTo
-// - experation
+// - expiration
// - messageId
// - timestamp
// - userId
Please sign in to comment.
Something went wrong with that request. Please try again.