[
https://issues.apache.org/jira/browse/PROTON-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297527#comment-16297527
]
Tim Taylor edited comment on PROTON-1718 at 12/19/17 10:27 PM:
---------------------------------------------------------------
Yes, my issue is more to do with how the Reactor does not allow users enough
control over the Sasl operations in the ways that I outlined above.
Ignore the point of sending multiple init frames, I was mistaken. I do not need
to be able to do that.
I'll try exploring the possibility of a fix that is more tied to the reactor.
was (Author: timtay):
Yes, my issue is more to do with how the Reactor does not allow users to alter
the Sasl operations in the ways that I outlined above.
Ignore the point of sending multiple init frames, I was mistaken. I do not need
to be able to do that.
I'll try exploring the possibility of a fix that is more tied to the reactor.
> (Proton-J) Custom Sasl
> ----------------------
>
> Key: PROTON-1718
> URL: https://issues.apache.org/jira/browse/PROTON-1718
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
> Affects Versions: proton-j-0.24.0
> Reporter: Tim Taylor
> Labels: features
>
> I would like to be able to provide a custom SASL implementation for Proton-j
> to use instead of being forced to use the default SaslImpl.java
> implementation.
> Ideally, code like below would be possible
> private class CustomSasl implements org.apache.qpid.proton.engine.Sasl
> {
> ...
> }
> ...
> ...
> //transport.sasl(...) saves the provided sasl implementation and uses it
> internally
> Sasl sasl = transport.sasl(new CustomSasl());
> Do you currently have a workaround that would allow me to use Proton-J this
> way?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
