[ https://issues.apache.org/jira/browse/PROTON-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505408#comment-13505408 ]
Gordon Sim commented on PROTON-160: ----------------------------------- I greatly prefer option (3) as outlined at the end of comment #1(https://issues.apache.org/jira/browse/PROTON-160?focusedCommentId=13505199), i.e. having some way to configure a messenger to handle addresses (falling back to DNS based resolution if no rules exist/apply). Per-message addresses should ideally be logical with a flexible mapping to the physical addresses over which they should then be transferred. Option 3 seems the safest and neatest solution. I find option 1 confusing as well as I think being to tied to a particular pattern of use. I thinks URLs are actually a less than ideal choice for the address syntax as they confuse the notions of (hierarchical) domain scoped logical naming with 'connection strings', and adding in various options and parameters is I think the thin end of the wedge that will lead to muddiness. > Allow open.hostname to be configured independently of network hostname > ---------------------------------------------------------------------- > > Key: PROTON-160 > URL: https://issues.apache.org/jira/browse/PROTON-160 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c > Affects Versions: 0.1, 0.2 > Reporter: David Ingham > > In a scaled-out, multi-tenant broker environment, the host on which the > container is running is often different from the host to which a client is > establishing the tcp connection. The 'hostname' field in the connection open > performative was added to support this scenario. Currently there's no way to > control this from the Messenger API. > Options include: > (1) (preferred) add a new 'networkhost' field to Message to allow the network > address to be specified. If provided, this information would be used when > establishing the network connection and the data in the 'address' field would > be used in the connection open hostname field. This is somewhat in line with > the way that connection redirect (amqp:connection:redirect) is specified. > (2) extend the syntax of address with query string to supply hostname, e.g., > username:password@tcpaddress:tcpport/entityname?hostname=foo where 'foo' > would become the hostname used in the connection open frame. This is the > approach used by the current Qpid AMQP 1.0 JMS client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira