Closed ar4mirez closed 8 years ago
I thought about this as well, I need contentEncoding.
I was thinking of specifying an array of allowed options for publish and merging those. Some just don't make sense such as correlationId, messageId and timestamp as they are message specific. Unless those options were defined as a function then we could pass the chunk and encoding into the function and set the option value to the result of that function.
@sberryman Agree with you :+1: I try to help with this PR but has been a year already so I'm not sure if will be merged some day or if there any other alternative ?
was trying to use some of the options from amqplib but i found the
setsockopt
function din't allow for extra options, and also the variable options in the functionPubSocket.prototype.publish
was overriding any new option set with setsockopt.http://www.squaremobius.net/amqp.node/doc/channel_api.html
I'm only adding publish#contentType for now but i can add more later on.