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/10/30 11:50:12 UTC
[jira] [Resolved] (BOOKKEEPER-366) hedwig protocol changes to
support multiplexing subscription channels.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sijie Guo resolved BOOKKEEPER-366.
----------------------------------
Resolution: Won't Fix
The protocol changes are already included in the sub tasks under BOOKKEEPER-70.
> hedwig protocol changes to support multiplexing subscription channels.
> ----------------------------------------------------------------------
>
> Key: BOOKKEEPER-366
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-366
> Project: Bookkeeper
> Issue Type: Sub-task
> Reporter: Sijie Guo
> Assignee: Sijie Guo
>
> In order to support multiplexing, we needs following protocol changes in Hedwig.
> 1) add a CloseSubscription request.
> currently closeSubscription is directly close the channel. but for a multiplexing channel, we should not close the channel directly. we need to send CloseSubscription request to hub server to tell hub server close subscription (stopServingSubscriber)
> 2) add a QueryOwner request type.
> for a multiplexing channel, we had to know the topic owner first and submit the subscribe request to the channel established to topic owner.
> 3) add a SubscriptionEventResponse response.
> in multiplexing mode, hub server should not close the channel directly when topic is release periodically or force closed by other subscription (introduced in BOOKKEEPER-252). so hub server needs to notify the clients that a topic is released or subscription is forced closed.
> the subscription event response carries an event to tell client what happened to the subscription.
--
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