Re: 答复: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

same time while in practical situation. > > > > > > Also, the same idea in Consumer-Broker Communication. > > > > > > > > > About consensus algorithm, I think RocketMQ should already have an > > > implementation there. I don't know what it is

Re: 答复: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

o implement one, in my opinion, there's no > need > > to implement both Paxos and Raft. Since they solve the same kind of > > problems. > > > > > > > > Regards, > > > > Dexin > > > > > > >

Re: 答复: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

. > > > > Regards, > > Dexin > > > ____ > 发件人: Sohaib Iftikhar <sohaib1...@gmail.com> > 发送时间: 2018年3月7日 18:15:51 > 收件人: dev@rocketmq.apache.org > 主题: Re: [GSOC|ROCKETMQ-124] Support non-redundant message delivery > mech

Re: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

Hi Yukon, Thanks for your reply. Yes, it would be nice to concretely define the scope of this project as the doc is a bit ambitious for just a summer. Should you (or anyone else) have questions/suggestions/clarifications I'd be glad to discuss more details. Thanks, Sohaib On Wed, Mar 7, 2018 at

Re: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

Hi, @Yukon Thank you for your reply. This clears some doubts. Sorry for the delay as I was somewhat occupied with another project. I have created an initial design doc. Email is a bit cumbersome for feedback I wrote this document in two formats: 1. In the form of a Google document:

Re: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

Hi Sohaib, I have been sort of busy this these days. Sorry to reply you so late! So sure what “deadline” you are referring to. If this is part of a campaign, I have to admit I am not aware of the regulations and what kind of help I should offer to maintain fairness considering other arising

Re：[GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

SOC|ROCKETMQ-124] Support non-redundant message delivery mechanism Hi guys, Would be nice to have some feedback on this as the deadline is not too far :) Thanks,Sohaib Regards, Sohaib Iftikhar -- Man is still the most extraordinary computer of all.-- On Mon, Feb 26, 2018 at 10:36 AM, Sohaib Iftik

Re: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

Hi Zhanhui, I have a doubt about these multiple keys. If I am wrong in any of the assumptions I make please point it out. If there is support for multiple keys I cannot see this in the code. The class Message only stores a single key in the property map against the property name "KEYS". Is this

Re: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

Hi Sohaib, Happy to know you are interested in RocketMQ. First, let me answer questions you raised. — can there be multiple tags? No. At present, the storage engine allows single tag only. Subscriptions are allowed to use combination of tags. The current model should meet your business

Re: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

My earlier email message seems to have gotten lost. So I will try again. Please see the original message for the discussion. Regards, Sohaib Iftikhar -- Man is still the most extraordinary computer of all.-- On Tue, Feb 20, 2018 at 1:54 AM, Sohaib Iftikhar wrote: > Hi, >

[GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

Hi, I am interested in working on this issue ( https://issues.apache.org/jira/browse/ROCKETMQ-124) as part of GSOC-18. I have a few questions for the same. I am not sure if this discussion needs to be on the JIRA issue or here. Feel free to correct me if this is the wrong platform. Also while I