You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org> on 2007/01/29 11:41:49 UTC

[jira] Created: (QPID-324) [performance] Only send byte indicating topic / queue / other in properties field table, not whole destination

[performance] Only send byte indicating topic / queue / other in properties field table, not whole destination
--------------------------------------------------------------------------------------------------------------

                 Key: QPID-324
                 URL: https://issues.apache.org/jira/browse/QPID-324
             Project: Qpid
          Issue Type: Improvement
          Components: Java Client
            Reporter: Rob Godfrey
            Priority: Minor


Currently we encode the whole destination in a byte[] in the field table so that we may do destination comparisons as per JMS Spec.

Since exchange and routingKey are already sent in the message, to get the same result all we need to add is whether the destination was considered a queue or a topic at the time it was sent.

Note that this is not a final solution for the more general issue:

We still need to describe what a destination actually is - do we need a unique global naming for [virtual] hosts; and how does bridging affect the exchange/routingKey sent in the deliver method.  We may need to add the original host/exchange/key as properties of the deliver method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (QPID-324) [performance] Only send byte indicating topic / queue / other in properties field table, not whole destination

Posted by "Robert Greig (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Greig resolved QPID-324.
-------------------------------

       Resolution: Fixed
    Fix Version/s: M2

Patch applied svn revision 501005

> [performance] Only send byte indicating topic / queue / other in properties field table, not whole destination
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-324
>                 URL: https://issues.apache.org/jira/browse/QPID-324
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>            Reporter: Rob Godfrey
>            Priority: Minor
>             Fix For: M2
>
>         Attachments: QPID-324.patch
>
>
> Currently we encode the whole destination in a byte[] in the field table so that we may do destination comparisons as per JMS Spec.
> Since exchange and routingKey are already sent in the message, to get the same result all we need to add is whether the destination was considered a queue or a topic at the time it was sent.
> Note that this is not a final solution for the more general issue:
> We still need to describe what a destination actually is - do we need a unique global naming for [virtual] hosts; and how does bridging affect the exchange/routingKey sent in the deliver method.  We may need to add the original host/exchange/key as properties of the deliver method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (QPID-324) [performance] Only send byte indicating topic / queue / other in properties field table, not whole destination

Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey updated QPID-324:
-----------------------------

    Attachment: QPID-324.patch

> [performance] Only send byte indicating topic / queue / other in properties field table, not whole destination
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-324
>                 URL: https://issues.apache.org/jira/browse/QPID-324
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>            Reporter: Rob Godfrey
>            Priority: Minor
>         Attachments: QPID-324.patch
>
>
> Currently we encode the whole destination in a byte[] in the field table so that we may do destination comparisons as per JMS Spec.
> Since exchange and routingKey are already sent in the message, to get the same result all we need to add is whether the destination was considered a queue or a topic at the time it was sent.
> Note that this is not a final solution for the more general issue:
> We still need to describe what a destination actually is - do we need a unique global naming for [virtual] hosts; and how does bridging affect the exchange/routingKey sent in the deliver method.  We may need to add the original host/exchange/key as properties of the deliver method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (QPID-324) [performance] Only send byte indicating topic / queue / other in properties field table, not whole destination

Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey reassigned QPID-324:
--------------------------------

    Assignee: Rob Godfrey

> [performance] Only send byte indicating topic / queue / other in properties field table, not whole destination
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-324
>                 URL: https://issues.apache.org/jira/browse/QPID-324
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>            Reporter: Rob Godfrey
>         Assigned To: Rob Godfrey
>            Priority: Minor
>             Fix For: M2
>
>         Attachments: QPID-324.patch
>
>
> Currently we encode the whole destination in a byte[] in the field table so that we may do destination comparisons as per JMS Spec.
> Since exchange and routingKey are already sent in the message, to get the same result all we need to add is whether the destination was considered a queue or a topic at the time it was sent.
> Note that this is not a final solution for the more general issue:
> We still need to describe what a destination actually is - do we need a unique global naming for [virtual] hosts; and how does bridging affect the exchange/routingKey sent in the deliver method.  We may need to add the original host/exchange/key as properties of the deliver method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.