You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <ji...@apache.org> on 2011/07/07 14:34:16 UTC
[jira] [Commented] (QPID-3342) Rationalise transport layer by
introducing common interfaces shared by all protocols
[ https://issues.apache.org/jira/browse/QPID-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061252#comment-13061252 ]
Rajith Attapattu commented on QPID-3342:
----------------------------------------
Keith,
Is this different from the work Andrew Kennedy is doing?
And is the NetworkTransport interface you are referring to is a new one or is it the one in org.apache.qpid.transport.network package ?
I have created a minimal abstraction for transports on the client side where transports implementing the NetworkTransport interface can be loaded via Reflection (See Transport.java and NetworkTransport.java in org.apache.qpid.transport.network)
Wondering what your thoughts are on that ?
Rajith
> 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: Keith Wall
> Fix For: 0.13
>
>
> 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