Bug 705788

Summary: [RFE] More detail and examples needed for 'Address String Options' section.
Product: Red Hat Enterprise MRG Reporter: Ken Giusti <kgiusti>
Component: Messaging_Programming_ReferenceAssignee: Joshua Wulf <jwulf>
Status: CLOSED DUPLICATE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: unspecified Docs Contact:
Priority: low    
Version: DevelopmentCC: alyoung, iboverma, jwulf, lcarlon, rafaels
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-13 09:26:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ken Giusti 2011-05-18 13:20:32 UTC
Description of problem:

I'll bet we'll get a lot of questions from the field on this topic.  Would it be possible to get a little more detail added to this section?

Specifically:

* What is the difference between "node" and "link" - when would I use one or the other?  I'm assuming they are mutually-exclusive.  Is "node" an AMQP-0.10 only concept, whereas the "link" option related to the new 1.0 model?

* I'm not clear on all the relevant uses of "create" and "delete" along with their options, and which options are nonsensical given a particular role (sender vs. receiver).  Specifically:

    1) Can we get a dedicated section that describes "delete", like we have for "create"?  It should contain examples of the common intended use-cases.  Like, can it be used to create a queue that auto-deletes after the last subscriber unsubscribes?  And what exactly does "delete: always" mean? 

* What does it mean to pass "create: receiver" to createSender(), or "create:sender" to createReceiver()?  Is this an invalid use of "create"?

Comment 4 Joshua Wulf 2013-05-13 09:26:12 UTC

*** This bug has been marked as a duplicate of bug 954473 ***