Andrew Stitcher commented on PROTON-970:

>From an API stand point I believe that different transports *should* be able 
>to have different configurations - unfortunately this is difficult (or perhaps 
>impossible) to implement with Cyrus SASL.

> SASL options for setting path and name should not be transport-specific
> -----------------------------------------------------------------------
>                 Key: PROTON-970
>                 URL: https://issues.apache.org/jira/browse/PROTON-970
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>            Reporter: Ted Ross
> Both pn_sasl_config_name and pn_sasl_config_path take a pn_sasl_t object as 
> an argument, suggesting that different transports may use different 
> configurations.
> Cyrus SASL treats both the path and (server) name as per-process settings.
> The above methods in pn_sasl should reflect this scope and not use a 
> pn_sasl_t as an argument.

This message was sent by Atlassian JIRA

Reply via email to