[ 
https://issues.apache.org/jira/browse/QPID-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217431#comment-13217431
 ] 

Rob Godfrey edited comment on QPID-792 at 2/27/12 7:31 PM:
-----------------------------------------------------------

We should really take this discussion off this JIRA and put it on the dev-list 
:-)

However... in answer to 

2. One that tries to resolve an address to see if it's indeed a Queue or a 
Topic (unless explicitly specified). This is a tricky one and the root cause of 
the TCK failures.

I don't think that we should be trying to do this because I'm pretty sure that 
it is impossible to determine what is a Queue and what is a Topic.

I think the closest we can come is to say that an address that says you have to 
create a new temporary auto-delete exclusive queue for every consumer should be 
treated as a topic... but the converse is not true.  As far as I am concerned 
the distinction between Queue and Topic is something that only the 
"administrator" can determine, and the code cannot determine dynamically.

 
                
      was (Author: rgodfrey):
    We should really take this discussion off this JIRA and put it on the 
dev-list :-)

So... in answer to 

                  
> Need to revise QueueBrowser implementation strategy
> ---------------------------------------------------
>
>                 Key: QPID-792
>                 URL: https://issues.apache.org/jira/browse/QPID-792
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>    Affects Versions: M3
>            Reporter: Rajith Attapattu
>            Assignee: Robbie Gemmell
>             Fix For: 0.15
>
>
> While debuggin and issue I noticed the following behaviour in the 
> AMQQueueBrowser class.
> 1) When we create a queue browser we do a subscribe immediately
> followed by a cancel. (And then we subscribe again when we enumerate).
> The rationale for doing so it to verify the selector is valid. This is
> very confusing for customers who look at the log and it is not appropriate 
> IMHO.
> Currently we use client side selectors, so it is easy validate this. The
> above step is completely unnecessary.
> If we are to use server side selectors the right way to do is
> a)Send a subscribe with the selector
> b)Give message credits only when you call the enumerate method.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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:[email protected]

Reply via email to