You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Pablo Guerrero (Created) (JIRA)" <ji...@apache.org> on 2012/04/20 15:44:43 UTC

[jira] [Created] (APLO-194) Protocol independent message abstraction

Protocol independent message abstraction
----------------------------------------

                 Key: APLO-194
                 URL: https://issues.apache.org/jira/browse/APLO-194
             Project: ActiveMQ Apollo
          Issue Type: New Feature
            Reporter: Pablo Guerrero


It would be really good to have a protocol independent message abstraction that allows plugins to perform actions independently of the protocol used. Some examples could be developing a protocol independent filter, or sending messages to destinations in a generic way, but I'm sure it would be useful in many other scenarios.

The message abstraction would need to abstract at least the concepts of headers and content of a message to be used in the scenarios described.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (APLO-194) Protocol independent message abstraction

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-194:
-------------------------------

    Fix Version/s: wish-list
    
> Protocol independent message abstraction
> ----------------------------------------
>
>                 Key: APLO-194
>                 URL: https://issues.apache.org/jira/browse/APLO-194
>             Project: ActiveMQ Apollo
>          Issue Type: New Feature
>            Reporter: Pablo Guerrero
>             Fix For: wish-list
>
>
> It would be really good to have a protocol independent message abstraction that allows plugins to perform actions independently of the protocol used. Some examples could be developing a protocol independent filter, or sending messages to destinations in a generic way, but I'm sure it would be useful in many other scenarios.
> The message abstraction would need to abstract at least the concepts of headers and content of a message to be used in the scenarios described.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira