You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2009/11/16 05:34:52 UTC

[jira] Updated: (AMQNET-191) Add New NMS Module NMS.Stomp

     [ https://issues.apache.org/activemq/browse/AMQNET-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes updated AMQNET-191:
-----------------------------

    Component/s: Stomp

> Add New NMS Module NMS.Stomp
> ----------------------------
>
>                 Key: AMQNET-191
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-191
>             Project: ActiveMQ .Net
>          Issue Type: New Feature
>          Components: Stomp
>    Affects Versions: 1.1.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 1.3.0
>
>
> Currently to use Stomp via NMS you must use the NMS.ActiveMQ project.  This brings with it a lot of extra code that you don't necessarily need or want and also limits support for all the features of the Stomp API on ActiveMQ (currently all Stomp NMS sessions are client Ack).
> By pulling out Stomp as its own module we can slim down the Stomp implementation and target that module to clients running on resource limited platforms running the .NET Compact Framework.  This will also allow for the stomp client to support future versions of the Stomp protocol more easily as it won't be tied to the implementation of the ActiveMQ client. 
> This task should result in a new Apache.NMS.Stomp module in SVN and a new Stomp JIRA category for NMS.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.