[
https://issues.apache.org/jira/browse/PROTON-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244267#comment-16244267
]
Alan Conway commented on PROTON-1682:
-------------------------------------
I vote for passing the transport to the proactor. Anything else involves
extensions to the event handling model that might have reprecussions elsewhere.
We will see similar issues for SASL.
The common pattern for bindings then becomes:
1. configure C pn_transport and pn_connection - using binding options from
connect(), listener.on_accept() and container
2. start IO and event processing - C/C++ uses proactor, ruby/go use
connection_driver + native IO.
3. handle events - common C event set for all bindings, presented in
binding-specific way as methods. virtual calls etc.
I think it was my mistake to hide transport configuration in the proactor - it
is a good idea for the bindings to merge the connection/transport concepts but
it was premature to try to do it at the C level where we still have a clear
separation of connection/transport configuration for security and vhost.
> SASL auth with GSSAPI fails: hostname is not set
> ------------------------------------------------
>
> Key: PROTON-1682
> URL: https://issues.apache.org/jira/browse/PROTON-1682
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, proton-c
> Affects Versions: proton-c-0.18.1
> Reporter: Andrew Stitcher
> Assignee: Cliff Jansen
> Fix For: proton-c-0.19.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
