On 05/28/2010 11:32 AM, Andrew Kennedy wrote:
On 28 May 2010 16:14, Alan Conway<[email protected]> wrote:
On 05/27/2010 03:18 PM, Kerry Bonin wrote:
I've been working on enabling SSL for our Windows& Python based
application. I've finally got silent root and server certificate
generators& installers working to bring up the brokers, now trying to
figure out how to specify an SSL connection using the messaging APIs.
Any pointers? Thanks...
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
Ignore previous message, here's exactly what the C++ URL parser parses
url = ["amqp:"][ user ["/" password] "@" ] protocol_addr *(","
protocol_addr)
protocol_addr = tcp_addr / rmda_addr / ssl_addr / .. others plug-in
tcp_addr = ["tcp:"] host [":" port]
rdma_addr = "rdma:" host [":" port]
ssl_addr = "ssl:" host [":" port]
does that really use a '/' as the username-password delimeter? it
probably should be changed to a ':', as in most other URI schemes, see
also RFC3986, section 3.2.1, which describes rendering of user
information in generic URIs...
I followed the lead of the python API which uses a similar URL format. I don't
know how many examples/tests there are that use the / separator. I don't feel
strongly either way but if we make the change we should do it across the board.
Rafi, what was the motivation for using "/" in the python URL?
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
