Ken Giusti closed PROTON-476.
       Resolution: Won't Fix
    Fix Version/s:     (was: 0.9)

Probably no longer necessary - the new attachments interface allows multiple 
contexts to be associated with the transport (which is the parent of both the 
SASL and SSL objects).

> Support a user-context for SASL and SSL objects.
> ------------------------------------------------
>                 Key: PROTON-476
>                 URL: https://issues.apache.org/jira/browse/PROTON-476
>             Project: Qpid Proton
>          Issue Type: New Feature
>          Components: proton-c
>    Affects Versions: 0.5
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
> For consistency and convenience, I'd like to add an API that would allow an 
> application-defined context be associated with the pn_sasl_t, 
> pn_ssl_domain_t, and pn_ssl_t objects.  This api would follow the convention 
> used by other proton classes (eg, pn_connection_get_context(), 
> pn_connection_set_context()).  ex:
> void *pn_sasl_get_context(pn_sasl_t);
> void pn_sasl_set_context(pn_sasl_t *, void *context); 

This message was sent by Atlassian JIRA

Reply via email to