Bug 825152 - [RFE] qpid c++ client Connection options string format should be available on all other qpid clients
Summary: [RFE] qpid c++ client Connection options string format should be available on...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: python-qpid
Version: 2.1.2
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-25 09:00 UTC by Frantisek Reznicek
Modified: 2020-11-04 19:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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