Bug 825152 - [RFE] qpid c++ client Connection options string format should be available on all other qpid clients
[RFE] qpid c++ client Connection options string format should be available on...
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: python-qpid (Show other bugs)
2.1.2
Unspecified Unspecified
low Severity unspecified
: ---
: ---
Assigned To: messaging-bugs
MRG Quality Engineering
: Improvement
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-25 05:00 EDT by Frantisek Reznicek
Modified: 2015-11-15 20:17 EST (History)
2 users (show)

See Also:
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: ---


Attachments (Terms of Use)

  None (edit)
Description Frantisek Reznicek 2012-05-25 05:00:30 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.