Mailing-List: contact proton-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: proton@qpid.apache.org
Date: Mon, 9 Dec 2013 15:58:07 +0000 (UTC)
From: "Ken Giusti (JIRA)" <jira@apache.org>
To: proton@qpid.apache.org
Message-ID: <JIRA.12683622.1386604577387.2970.1386604687470@arcas>
In-Reply-To: <JIRA.12683622.1386604577387@arcas>
References: <JIRA.12683622.1386604577387@arcas>
Subject: [jira] [Created] (PROTON-476) Support a user-context for SASL and
 SSL objects.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ken Giusti created PROTON-476:
---------------------------------

             Summary: 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
             Fix For: 0.6


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
(v6.1.4#6159)