New API request.

[Carl Trieloff <cc...@redhat.com>]

For connection open, any objections to adding a constructor that places
the contents of the URL, in parts in the options map.

     QPID_MESSAGING_EXTERN Connection(const std::string& url, const 
qpid::types::Variant::Map& options = qpid::types::Variant::Map());


i.e adding one without the 'url' while adding port, host etc as options 
to the map. being
asking myself, why should I need to string cat all the piece together, 
and do
parsing when I don't need to.

Carl.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

RE: New API request.

[Steve Huston <sh...@riverace.com>]

Hi Carl,

> For connection open, any objections to adding a constructor 
> that places the contents of the URL, in parts in the options map.
> 
>      QPID_MESSAGING_EXTERN Connection(const std::string& url, const 
> qpid::types::Variant::Map& options = qpid::types::Variant::Map());
> 
> 
> i.e adding one without the 'url' while adding port, host etc 
> as options to the map. being
> asking myself, why should I need to string cat all the piece 
> together, and do parsing when I don't need to.

Makes sense, yes. Maybe, though, separate host and port# arguments,
maybe instead of the url to reduce confusion and errors?

>   QPID_MESSAGING_EXTERN Connection(const std::string& host, const
uint16 port = 5672, 
>     const qpid::types::Variant::Map& options =
qpid::types::Variant::Map());

-Steve


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org