[
https://issues.apache.org/jira/browse/PROTON-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310063#comment-16310063
]
Tim Taylor commented on PROTON-1718:
------------------------------------
I want to set aside the talk of adding extra threads to this problem. I don't
think I will need to use separate threads for this scenario.
Instead, I want to drill down on part of your comment:
"When you 'send' for sasl (which doesnt actually send anything on the wire
immediately, only later when the IO processing occurs) is indeed important
since any IO work is only done explicitly at a stage of the thread processing
the reactor (which is often after processing received data off the wire)."
Is this the only time when the reactor does IO processing? I would like my
"send" calls to be processed, but there is no callback extended to the user
that allows them to react in time to catch the reactor in this phase. I would
imagine that there is some event that should be extended to users that allows
them to insert their challenge response when a given challenge is received.
Using sasl.Pending() isn't good enough to catch the reactor during this IO
phase.
Is there a way to tell the reactor to do IO processing at some arbitrary
reactor event (onReactorQuiesced, for example)?
> (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
