[
https://issues.apache.org/jira/browse/PROTON-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187378#comment-15187378
]
ASF subversion and git services commented on PROTON-1155:
---------------------------------------------------------
Commit 747ee17215d520b862c81ed4d15949e96da5a6a2 in qpid-proton's branch
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=747ee17 ]
PROTON-1155 - Modified BlockingConnection to pass **kwargs to the
container.connect call
> [proton-c] Add allowed_mechs to BlockingConnection constructor
> --------------------------------------------------------------
>
> Key: PROTON-1155
> URL: https://issues.apache.org/jira/browse/PROTON-1155
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: 0.12.0
> Reporter: Ganesh Murthy
> Priority: Minor
>
> In the Proton Python binding, currently there is no way to pass in
> allowed_mechs to BlockingConnection's constructor
> BlockingConnection's constructor should take in an allowed_mechs parameter.
> The Container object has a connect function
> {code}
> def connect(self, url=None, urls=None, address=None, handler=None,
> reconnect=None, heartbeat=None, ssl_domain=None, **kwargs):
> {code}
> The above function already sets the allowed_mechs on the Connector
> {code}
> connector.allowed_mechs = kwargs.get('allowed_mechs', self.allowed_mechs)
> {code}
> So BlockingConnection just needs to pass in the allowed_mechs and the rest is
> take care of by the Container
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
