You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/12/09 19:27:11 UTC

[jira] [Commented] (PROTON-1054) Add acceptor context to incoming reactor connections.

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

ASF subversion and git services commented on PROTON-1054:
---------------------------------------------------------

Commit d6da8eb1c534a5432fcf1b16db7e034f81db3314 in qpid-proton's branch refs/heads/master from Clifford Jansen
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d6da8eb ]

PROTON-1054: add acceptor context to incoming reactor connections.


> Add acceptor context to incoming reactor connections.
> -----------------------------------------------------
>
>                 Key: PROTON-1054
>                 URL: https://issues.apache.org/jira/browse/PROTON-1054
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-c
>    Affects Versions: 0.12.0
>            Reporter: Cliff Jansen
>            Assignee: Cliff Jansen
>             Fix For: 0.12.0
>
>         Attachments: diff44
>
>
> The reactor's acceptor currently intercepts the readable callback and sets up the incoming connection.  The only generated event is PN_CONNECTION_INIT with no context of the listener.
> This prevents implementing separate connection options based on listening interface/port.  One solution is to have the acceptor add context to each connection and provide a new API call to find the parent acceptor for a connection.



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