qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3342) Rationalise transport layer by introducing common interfaces shared by all protocols
Date Thu, 07 Jul 2011 19:52:16 GMT

    [ https://issues.apache.org/jira/browse/QPID-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061538#comment-13061538

Robbie Gemmell commented on QPID-3342:

Cross-posted comments. Yes, that JIRA is the final piece in the puzzle. As per Andrews previous
design, the pluggability will occur at the NetworkTansport level in similar fashion to the
previous 'getTransport' behaviour you added, with the building and lifecycle maintenance of
the Sender/Reciever pipes being the responsability of the NetworkConnections those NetworkTransports

> Rationalise transport layer by introducing common interfaces shared by all protocols
> ------------------------------------------------------------------------------------
>                 Key: QPID-3342
>                 URL: https://issues.apache.org/jira/browse/QPID-3342
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker, Java Client, Java Common
>            Reporter: Keith Wall
>            Assignee: Robbie Gemmell
>             Fix For: 0.13
>         Attachments: 0002-QPID-3342-rationalise-the-existing-0-10-transport-co.patch,
> Refactor the transport stack by introducing two new interfaces NetworkTransport and NetworkConnection.
  Remove dependencies between IoSender and IoReceiver.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message