[PROTON-160] Allow open.hostname to be configured independently of network hostname

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.1, proton-0.2
• Fix Version/s: proton-0.5
• Component/s: proton-c, proton-j
• Labels: api
• Assignee: Rafael H. Schloming
• Reporter: David Ingham
• Created: 26/Nov/12 21:19
• Updated: 07/Jan/16 11:33
• Resolved: 22/Aug/13 16:56

Description

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.