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

ASF subversion and git services commented on QPID-5548:
-------------------------------------------------------

Commit 1565819 from [email protected] in branch 'qpid/trunk'
[ https://svn.apache.org/r1565819 ]

QPID-5548: C++ Messaging API does not specify the connection Connection URL 
format
Add Connection section and Connection URLs subsection.
Demote Connection Options to be a subsection of Connection.

> C++ Messaging API does not specify the connection Connection URL format
> -----------------------------------------------------------------------
>
>                 Key: QPID-5548
>                 URL: https://issues.apache.org/jira/browse/QPID-5548
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Client, Documentation
>    Affects Versions: 0.27
>            Reporter: Chuck Rolke
>            Assignee: Chuck Rolke
>
> The Programming In Apache Qpid documentation never discusses the format of 
> the Connection URL string, the only required argument for constructing a 
> Messaging Connection. The URL is specified by AMPQ 0.10:
> {noformat}
> amqp_url = "amqp:" prot_addr_list
> prot_addr_list = [prot_addr ","]* prot_addr
> prot_addr = tcp_prot_addr | tls_prot_addr
> tcp_prot_addr = tcp_id tcp_addr
> tcp_id = "tcp:" | ""
> tcp_addr = [host [":" port] ]
> host = <as per http://www.ietf.org/rfc/rfc3986.txt>
> port = number
> {noformat}
> The C++ Messaging connection string is not the same as the JMS Connection
> http://qpid.apache.org/releases/qpid-0.24/programming/book/QpidJNDI.html#section-jms-connection-url
> This issue tracks adding a few lines to the documentation describing the 
> connection format.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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

Reply via email to