[ 
https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504348#comment-14504348
 ] 

ASF GitHub Bot commented on PROTON-334:
---------------------------------------

Github user dcristoloveanu commented on the pull request:

    https://github.com/apache/qpid-proton/pull/19#issuecomment-94641331
  
    I’ve removed the SASL client mechanism setter as I think PROTON-334 should 
do when it comes online. And if it does not we can always bring this back in 
another pull request. One small thing at a time.
    
    Thanks for the feedback.
    
    /Dan
    
    From: Rafael Schloming [mailto:notificati...@github.com]
    Sent: Monday, April 20, 2015 5:27 AM
    To: apache/qpid-proton
    Cc: Dan Cristoloveanu
    Subject: Re: [qpid-proton] Mbed minor changes and sasl mech (#19)
    
    
    @astitcher<https://github.com/astitcher>: do you want to wait until 
PROTON-334 lands to pull this in given the conflict you mention?
    
    —
    Reply to this email directly or view it on 
GitHub<https://github.com/apache/qpid-proton/pull/19#issuecomment-94438477>.



> SASL Implementation for Proton C
> --------------------------------
>
>                 Key: PROTON-334
>                 URL: https://issues.apache.org/jira/browse/PROTON-334
>             Project: Qpid Proton
>          Issue Type: Wish
>          Components: proton-c
>            Reporter: Ted Ross
>            Assignee: Andrew Stitcher
>
> It would be desirable to have the ability to use a plug-in module for SASL in 
> Proton.  The following implementations could then be developed:
> 1) A portable stand-alone plugin that does ANONYMOUS, PLAIN, and EXTERNAL
> 2) A Cyrus-Sasl based plugin for Linux
> 3) A Windows plugin



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to