You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@stratos.apache.org by "Anuruddha Lanka Liyanarachchi (JIRA)" <ji...@apache.org> on 2015/05/14 11:48:01 UTC

[jira] [Updated] (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:all-tabpanel ]

Anuruddha Lanka Liyanarachchi updated STRATOS-968:
--------------------------------------------------
    Fix Version/s: 4.1.0 RC1

> 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 Beta, 4.1.0 RC1
>
>
> 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)