You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <ji...@apache.org> on 2011/02/24 12:10:38 UTC
[jira] Resolved: (QPID-2714) "Programming in Apache Qpid" doesn't
discuss capacity/credit
[ https://issues.apache.org/jira/browse/QPID-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim resolved QPID-2714.
------------------------------
Resolution: Fixed
> "Programming in Apache Qpid" doesn't discuss capacity/credit
> ------------------------------------------------------------
>
> Key: QPID-2714
> URL: https://issues.apache.org/jira/browse/QPID-2714
> Project: Qpid
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 0.7
> Reporter: Steve Huston
> Priority: Minor
> Attachments: QPID-2714.patch
>
>
> My comments grew out of looking at the C++ messaging API, though this probably applies to Python and .NET as well.
> During a discussion on users@qpid I initiated recently I learned that creating a number of Receivers and calling session.nextReceiver() to wait for a message on any of the Receivers doesn't work unless some capacity is granted to the Receivers first. This is different from simply calling fetch() on a Receiver with no capacity - in that case the client code issues credit behind the scenes.
> The code example shown in section 6 won't work (I used something very similar in a program I wrote, and it didn't for the reason above). I'll attach a patch that fixes the C++ code example, but there should be an introduction/discussion of the whole topic of capacity, credit, acks, etc.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org