Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of gsim@redhat.com designates
 209.132.183.28 as permitted sender)
Message-ID: <53723859.1090508@redhat.com>
Date: Tue, 13 May 2014 16:20:57 +0100
From: Gordon Sim <gsim@redhat.com>
Organization: Red Hat UK Ltd, Registered in England and Wales under Company
 Registration No. 3798903, Directors: Michael Cunningham (USA), Matt Parsons
 (USA), Charlie Peters (USA), Michael O'Neill (Ireland)
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: "users@qpid.apache.org" <users@qpid.apache.org>, dev@activemq.apache.org
Subject: AMQP 1.0 connection property names
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

The qpid::messaging (c++), qpid.messaging (python) libraries send 
connection properties to identify the process by name and pid among 
other things. These are then used by the QMF support in qpidd to report 
the process details for the connections.

This has proven to be an extremely useful feature and is supported also 
over AMQP 1.0. At present the property names used for both 0-10 and 1.0 
are qpid.client_pid and qpid.client_process.

However I would like to send this data in an application outside of 
qpid[1]. Having standard names for these two items over AMQP 1.0 would 
be great. This is not to force any implementation that doesn't support 
or recognise them to do so, merely to encourage anyone adding something 
similar to use the same property name for better interoperability.

I'm open to any suggestions on the names to use, but I would like to 
submit a request to OASIS to have them added to 
http://www.amqp.org/specification/1.0/connection-properties. My 
suggestion is simply to use 'pid' and 'process'.

Anyone have an opinion on this? If not I'll go ahead and send a request 
to https://lists.oasis-open.org/archives/amqp-comment/

Apologies for the cross-posting, but I figured there may be interest on 
the ActiveMQ side as well.

--Gordon.

[1] Specifically a proposed 'driver' supporting AMQP 1.0 in OpenStack's 
messaging library: https://github.com/FlaPer87/oslo.messaging/tree/gordon

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org