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

update documentation

This commit is contained in:
Emiel Bruijntjes 2014-04-15 14:33:40 +02:00
parent 44a9dff413
commit b043c33cc6
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

@ -287,8 +287,8 @@ myChannel.onReady([]() {
}); });
```` ````
In theory, you should always use the onReady() function before you send any In theory, you should wait for the onReady() callback to be called before you
other instructions over the channel. In practive however, the AMQP library send any other instructions over the channel. In practice however, the AMQP library
caches all instructions that were sent too early, so that you can use the caches all instructions that were sent too early, so that you can use the
channel object right after it was constructed. channel object right after it was constructed.
@ -562,7 +562,7 @@ DeferredConsumer &consume(const std::string &queue, const AMQP::Table &arguments
```` ````
As you can see, the consume method returns a DeferredConsumer. This object is a As you can see, the consume method returns a DeferredConsumer. This object is a
regular Deferred, with the some additions. The onSuccess() method of a regular Deferred, with additions. The onSuccess() method of a
DeferredConsumer is slightly different than the onSuccess() method of a regular DeferredConsumer is slightly different than the onSuccess() method of a regular
Deferred object: one extra parameter will be supplied to your callback function Deferred object: one extra parameter will be supplied to your callback function
with the consumer tag. with the consumer tag.