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

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/01/14 15:44:14 UTC

[jira] [Commented] (BOOKKEEPER-309) Protocol changes in hedwig to support JMS spec

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552690#comment-13552690 ] 

Ivan Kelly commented on BOOKKEEPER-309:
---------------------------------------

This was committed with BOOKKEEPER-331

                
> Protocol changes in hedwig to support JMS spec
> ----------------------------------------------
>
>                 Key: BOOKKEEPER-309
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-309
>             Project: Bookkeeper
>          Issue Type: Sub-task
>            Reporter: Mridul Muralidharan
>            Assignee: Mridul Muralidharan
>             Fix For: 4.2.0
>
>         Attachments: hedwig-protocol.patch, hedwig-protocol.patch.1, hedwig-protocol.patch.3, hedwig-protocol.patch.4, hedwig-protocol.patch.5
>
>
> JMS spec compliance requires three changes to the protocol.
> a) Support for message properties.
> b) Make body optional (message contains only properties).
> c) Return the published message's seq-id in the response.

--
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