jessequ
/
AMQP-CPP
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #256 from 0xflotus/patch-1 

fixed some typos
This commit is contained in:
Emiel Bruijntjes 2018-10-27 12:29:47 +02:00 committed by GitHub
parent 5f06c453b4 97aaa4beaf
commit 5836ab88d9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -254,7 +254,7 @@ this buffer. The code snippet below comes from the Connection.h C++ header file.
````c++ ````c++
/** /**
* Parse data that was recevied from RabbitMQ * Parse data that was received from RabbitMQ
* *
* Every time that data comes in from RabbitMQ, you should call this method to parse * Every time that data comes in from RabbitMQ, you should call this method to parse
* the incoming data, and let it handle by the AMQP-CPP library. This method returns * the incoming data, and let it handle by the AMQP-CPP library. This method returns
@ -941,7 +941,7 @@ DeferredPublisher &publish(const std::string &exchange, const std::string &routi
```` ````
Published messages are normally not confirmed by the server, and the RabbitMQ Published messages are normally not confirmed by the server, and the RabbitMQ
will not send a report back to inform you whether the message was succesfully will not send a report back to inform you whether the message was successfully
published or not. But with the flags you can instruct RabbitMQ to send back published or not. But with the flags you can instruct RabbitMQ to send back
the message if it was undeliverable. the message if it was undeliverable.
@ -994,7 +994,7 @@ positive and negative acknowledgments handling are implemented as callbacks for
````c++ ````c++
// setup confirm mode and ack/nack callbacks // setup confirm mode and ack/nack callbacks
channel.confirmSelect().onSuccess([&]() { channel.confirmSelect().onSuccess([&]() {
// from this moment onwards ack/nack confirmations are comming in // from this moment onwards ack/nack confirmations are coming in
channel.publish("my-exchange", "my-key", "my first message"); channel.publish("my-exchange", "my-key", "my first message");
// message counter is now 1, will call onAck/onNack with deliverTag=1 // message counter is now 1, will call onAck/onNack with deliverTag=1