You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Imesh Gunaratne (JIRA)" <ji...@apache.org> on 2014/11/15 07:10:33 UTC
[jira] [Commented] (STRATOS-968) Introduce an Abstraction between
Message Broker Transport and Messaging Component Implementation
[ https://issues.apache.org/jira/browse/STRATOS-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213405#comment-14213405 ]
Imesh Gunaratne commented on STRATOS-968:
-----------------------------------------
Fixed with commit revision: 87ab43d0bf43373d813483494c551e8f69b7a4f8
> Introduce an Abstraction between Message Broker Transport and Messaging Component Implementation
> ------------------------------------------------------------------------------------------------
>
> Key: STRATOS-968
> URL: https://issues.apache.org/jira/browse/STRATOS-968
> Project: Stratos
> Issue Type: Improvement
> Affects Versions: 4.1.0 M4
> Reporter: Imesh Gunaratne
> Assignee: Imesh Gunaratne
> Fix For: 4.1.0 M5
>
>
> Currently in the messaging component there is no abstraction found between the message broker transport and messaging implementation. All the publisher/subscriber/listener classes are directly referring MQTT library classes.
> IMO it would be better to have such abstraction because it will allow us to switch to a different transport with less effort without having to update the entire messaging component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)