[
https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407756#comment-13407756
]
Mridul Muralidharan commented on BOOKKEEPER-309:
------------------------------------------------
.bq How is the proposal to add MessageHeader I proposed in BOOKKEEPER-78?
Without type information, any attempts to filtering will be broken.
More specifically, in case of JMS, there are strict rules in terms of
conversion between types - which cant be inferred without the type.
.bq regarding splitting into different jira's.
As I explained before, and the reason I grouped the jira's as tasks under a
single umbrella JIRA, is because the tasks are unfortunately interdependent.
I do understand it makes reviewing them a bit of a pain, and the inability to
apply them separately - but they cant be split and applied independently
(except for server changes I guess) due to overlap.
Unfortunately, I do not have the cycles to try to create additional 4 partial
workspaces for this : which wont be functionally complete in case of (2) and
(3), or untestable - in case of only (1); and unusable/broken - in case of only
(4).
Having said that, the individual diff's currently in the jira's loosely follow
this already - (2) and (3) are mostly split along consume and publish whereever
possible, but are not independently applicable due to hedwig code level overlap.
Hope you understand.
> 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
> Attachments: hedwig-protocol.patch, hedwig-protocol.patch.1
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
