You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2012/07/23 13:07:34 UTC

[jira] [Commented] (BOOKKEEPER-350) Revisit consume interface in Hedwig Client

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

Sijie Guo commented on BOOKKEEPER-350:
--------------------------------------

@sijie:

for consume request:

1) the changes break backward compatibility. it changed the consume semantic. if existed applications used consume as async callback, it broken existed applications' assumption. one way I think we might not change consume's semantic, adding another call which returns only when consume request is written to the channel. this new call name might be 'syncConsume' or other better name.

2) even we have 'syncConsume' like method to ensure netty wrote the consume request to server. we still can't guarantee the consume request is received and processed by hub server. so adding such 'syncConsume' could not provide any semantic guarantee to the consume behavior.

what kind of semantic for consume request is needed by JMS provider? the request is wrote to the channel? the request is processed by the hub sever?
                
> Revisit consume interface in Hedwig Client
> ------------------------------------------
>
>                 Key: BOOKKEEPER-350
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-350
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: hedwig-client
>    Affects Versions: 4.0.0, 4.1.0
>            Reporter: Sijie Guo
>             Fix For: 4.2.0
>
>
> the jira is used to revisit consume interface in hedwig client and to improve it to meet JMS provider's requirements.
> move comments from BOOKKEEPER-311 to here, which make discussion more clearer. 

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