[
https://issues.apache.org/jira/browse/BOOKKEEPER-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401931#comment-13401931
]
Sijie Guo commented on BOOKKEEPER-309:
--------------------------------------
I don't like the idea to put JMS related spec in hedwig protocol. from my
understanding, JMS would be a kind of protocol sits on top of Hedwig, so a JMS
message would be the body of hedwig message.
I'd prefer to make the hedwig protocol independent from other protocols (like
JMS, stomp). So if user want to use JMS, it could use hedwig-jms-client; if
user want to use stomp protocol, there might be a separated module
hedwig-stomp-client working on stomp protocol.
{quote}
In fact, I'm inclined to think there should only be a 'bytes' value type, and
leave it up to the application to decode it correctly. Sijie was talking about
adding metadata recently, so we should also discuss this with him.
{quote}
Yes. I agreed Ivan's idea. Adding a generic header (properties: string key,
bytes value) part of Hedwig Message would be a good idea. so different
protocols sits on top of hedwig could leverage the header part to store its
customized data, which might be used to filter message without looking into
message body.
FYI: Stomp protocol : http://stomp.github.com//stomp-specification-1.1.html
> 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
>
>
> 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
