Bug 825152

Summary: [RFE] qpid c++ client Connection options string format should be available on all other qpid clients
Product: Red Hat Enterprise MRG Reporter: Frantisek Reznicek <freznice>
Component: python-qpidAssignee: messaging-bugs <messaging-bugs>
Status: NEW --- QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: unspecified Docs Contact:
Priority: low    
Version: 2.1.2CC: jross
Target Milestone: ---Keywords: Improvement
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frantisek Reznicek 2012-05-25 09:00:30 UTC
Description of problem:

qpid c++ client API allows to specify connection options using simple string format:
  Connection (const std::string &url, const std::string &options)
     Creates a connection using an option string of the form
     {name:value,name2:value2...}, see above for options supported. 

This way of connection option specification is very convenient and should be supported across all other languages. (specifically python API does not support it)



Version-Release number of selected component (if applicable):
2.1.2 qpid-0.14

How reproducible:
N/A

Steps to Reproduce:
1. see documantation on qpid::messaging::Connection
2. see documentation on qpid.messaging.Connection (pydoc qpid.messaging.Connection)
  
Actual results:
String-like connection options available in c++ client is not in other client libs.

Expected results:
String-like connection options available in c++ client should be available in other client libs.