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

Rob Godfrey commented on QPID-6161:
-----------------------------------

Addressed points 1,2 4 and 5 for HostNameAliasImpl addressed.  Point 3 I don't 
really see as a performance issue, and by having it per port then we can 
potentially stop/start the port and refresh the information (when we support 
state changes on ports) rather than having to stop/start the whole broker.

On PatternMatchingAliasImpl, I've added validation to make sure only valid 
values are set.  I've not saved the precompiled pattern as I don't think that 
performance here is going to be critical (it's only called on connection 
establishment which should never be critical path).

> [Java Broker] Add support for virtual host aliasing
> ---------------------------------------------------
>
>                 Key: QPID-6161
>                 URL: https://issues.apache.org/jira/browse/QPID-6161
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Rob Godfrey
>            Assignee: Rob Godfrey
>             Fix For: 0.31
>
>
> Add the ability to configure how a connection request for a given 
> "host"/"virtualhost" is translated to assigning to a virtual host inside the 
> broker.  Allow for multiple names to match the same virtualhost, for 
> different ports to have different mappings, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to