You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2017/03/01 15:26:45 UTC

[jira] [Updated] (ARTEMIS-971) The WildcardConfiguration manager could be optimized in MQTT

     [ https://issues.apache.org/jira/browse/ARTEMIS-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram updated ARTEMIS-971:
-----------------------------------
    Description: 
The WildcardConfiguration manager will search and replace MQTT wildcards with the configured wildcards.  This is an O\(n) operation for each message as the manager iterates over each char in the address string.

In some cases when the configured configured wildcards match the MQTT wildcards we can ignore this completely.

  was:
The WildcardConfiguration manager will search and replace MQTT wildcards with the configured wildcards.  This is an O(n) operation for each message as the manager iterates over each char in the address string.

In some cases when the configured configured wildcards match the MQTT wildcards we can ignore this completely.


> The WildcardConfiguration manager could be optimized in MQTT
> ------------------------------------------------------------
>
>                 Key: ARTEMIS-971
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-971
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Martyn Taylor
>
> The WildcardConfiguration manager will search and replace MQTT wildcards with the configured wildcards.  This is an O\(n) operation for each message as the manager iterates over each char in the address string.
> In some cases when the configured configured wildcards match the MQTT wildcards we can ignore this completely.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)