Re: Random CI falling on jdk11

[Yuhao Bi]

I have sent a PR [1] for this issue, I believe it will solve this.

[1]. https://github.com/apache/incubator-dubbo/pull/3327

Huxing Zhang  于2019年1月24日周四 下午3:48写道：

> Hi Yuhao,
>
> Thanks for taking care of this!
>
> On Thu, Jan 24, 2019 at 2:25 PM Yuhao Bi  wrote:
> >
> > Hi there,
> >
> > Our CI is experiencing random falling on test case
> > DubboMonitorTest#testCount.
> > I just experienced once yesterday [1], and now on our master branch [2].
> > Seems it's more like to happen in jdk11.
> > I will do some dig.
> >
> > Thanks,
> > Yuhao
> >
> > [1]. https://travis-ci.org/apache/incubator-dubbo/jobs/483426272
> > [2]. https://travis-ci.org/apache/incubator-dubbo/jobs/483735494
>
>
>
> --
> Best Regards！
> Huxing
>

Re: Random CI falling on jdk11

[Huxing Zhang]

Hi Yuhao,

Thanks for taking care of this!

On Thu, Jan 24, 2019 at 2:25 PM Yuhao Bi  wrote:
>
> Hi there,
>
> Our CI is experiencing random falling on test case
> DubboMonitorTest#testCount.
> I just experienced once yesterday [1], and now on our master branch [2].
> Seems it's more like to happen in jdk11.
> I will do some dig.
>
> Thanks,
> Yuhao
>
> [1]. https://travis-ci.org/apache/incubator-dubbo/jobs/483426272
> [2]. https://travis-ci.org/apache/incubator-dubbo/jobs/483735494



-- 
Best Regards！
Huxing

Re: about to open source a metrics sdk

[Huxing Zhang]

Hi,


On Thu, Jan 24, 2019 at 11:48 AM Minxuan Zhuang  wrote:
>
> Hi all:
> I'm planning to open source a metrics sdk implemented in java, and
> use it as the default metrics implementation for dubbo. since it's an
> initial version, I want to put it under dubbo group for now.

+1 to place under Dubbo group, and let the community to evaluate for a while.
If it is suitable and mature, I think we should transfer it to Apache.

-- 
Best Regards！
Huxing

Re: Re: discuss opentracing

[发给官兵]

Got it. Thank you!

zhi_guang_...@163.com  于2019年1月24日周四 下午2:47写道：

> Hi
> If you just want to STUDY USE Dubbo. I think the official document is
> enough.
>
> http://dubbo.apache.org/zh-cn/docs/user/quick-start.html
>
> It's how to use dubbo.
>
>
> --
> 您的朋友：刘志广
> 电话：18618457227QQ：42286866
>
>
> *From:* 发给官兵 
> *Date:* 2019-01-24 14:41
> *To:* dev 
> *Subject:* Re: discuss opentracing
> Thank you! I'm here for study dubbo. What could I describe? Are there some
> pages that I can see?
>
> Huxing Zhang  于2019年1月24日周四 上午11:06写道：
>
> > Hi,
> >
> > Welcome to the community!
> > There is no content in your email, would you please describe more of
> > what you want to discuss?
> >
> > On Wed, Jan 23, 2019 at 3:25 PM Ma Xiaoguang 
> > wrote:
> >
> > --
> > Best Regards！
> > Huxing
> >
>
>

Re: Re: discuss opentracing

[zhi_guang_...@163.com]

Hi
If you just want to STUDY USE Dubbo. I think the official document is 
enough.

http://dubbo.apache.org/zh-cn/docs/user/quick-start.html 

It's how to use dubbo.




您的朋友：刘志广
电话：18618457227QQ：42286866

 
From: 发给官兵
Date: 2019-01-24 14:41
To: dev
Subject: Re: discuss opentracing
Thank you! I'm here for study dubbo. What could I describe? Are there some
pages that I can see?
 
Huxing Zhang  于2019年1月24日周四 上午11:06写道：
 
> Hi,
>
> Welcome to the community!
> There is no content in your email, would you please describe more of
> what you want to discuss?
>
> On Wed, Jan 23, 2019 at 3:25 PM Ma Xiaoguang 
> wrote:
>
> --
> Best Regards！
> Huxing
>

Re: discuss opentracing

[发给官兵]

Thank you! I'm here for study dubbo. What could I describe? Are there some
pages that I can see?

Huxing Zhang  于2019年1月24日周四 上午11:06写道：

> Hi,
>
> Welcome to the community!
> There is no content in your email, would you please describe more of
> what you want to discuss?
>
> On Wed, Jan 23, 2019 at 3:25 PM Ma Xiaoguang 
> wrote:
>
> --
> Best Regards！
> Huxing
>

Random CI falling on jdk11

[Yuhao Bi]

Hi there,

Our CI is experiencing random falling on test case
DubboMonitorTest#testCount.
I just experienced once yesterday [1], and now on our master branch [2].
Seems it's more like to happen in jdk11.
I will do some dig.

Thanks,
Yuhao

[1]. https://travis-ci.org/apache/incubator-dubbo/jobs/483426272
[2]. https://travis-ci.org/apache/incubator-dubbo/jobs/483735494

Re: about to open source a metrics sdk

[Taosheng, Wei]

Minxuan,
Good job!
Metrics of frameworks and applications are important! Welcome to open source it 
and apply to dubbo. We can learn to use it!




-- Original --
From: Minxuan Zhuang 
Date: Thu,Jan 24,2019 11:48 AM
To: dev 
Subject: Re: about to open source a metrics sdk



Hi all:
I'm planning to open source a metrics sdk implemented in java, and
use it as the default metrics implementation for dubbo. since it's an
initial version, I want to put it under dubbo group for now.

about to open source a metrics sdk

[Minxuan Zhuang]

Hi all:
I'm planning to open source a metrics sdk implemented in java, and
use it as the default metrics implementation for dubbo. since it's an
initial version, I want to put it under dubbo group for now.

Re: [Discuss] The Timer Design in Dubbo from 2.6 to 2.7

[yuhang xiu]

hi，all

回复一下关于引入timer的问题。关于第一个问题，是为了解决defaultFuture的timeout问题，其实这个问题在issue[1]里说的很清楚了，就是为了解决无效的遍历。
对比老的实现即可发现，老的遍历做了非常多的无用功，而timer可以更精确的控制超时。

关于netty为什么不使用的问题，我这里提交了一个issue[2]。

所有的其他讨论我认为应该在netty回复我们以后。

在使用场景上，dubbo确实有需求，在多级时间轮上，这个在引入的时候我也做过调查，并不是必须的，只要我们控制好timer的大小即可。
关于timer的逻辑耦合在抽象类，我其实没弄懂你的意思，timer当然可重用，你是想说timertask能否重用的问题么？timertask的抽象我们也可以通用（目前这里是有抽象空间的），另外timertask作为执行单元，task执行的效果不一样，当然不存在能否重用的问题，这个感觉就是schedulethreadpool执行的每个runnable都基本不太能复用是一个道理。

[1] https://github.com/apache/incubator-dubbo/issues/1371
[2] https://github.com/netty/netty/issues/8774


徐靖峰  于2019年1月24日周四 上午10:09写道：

> Hi, Jason，a nice opinion.
>
> I have noticed that this issue[1] in Github encourage  the change from
> Schedule to HashedWheelTimer, but didn’t give a vert detailed reason.
>
> Is HashedWheelTimer really an unquestionable choice?
>
> [1] https://github.com/apache/incubator-dubbo/issues/1371 <
> https://github.com/apache/incubator-dubbo/issues/1371>
>
> > 在 2019年1月24日，上午9:53，Jason Joo  写道：
> >
> > Maybe because the main scenario dubbo faces is persistent connection.
> > For persistent connections the most frequent thing is ticking.
> >
> > ScheduledThreadPoolExecutor is O(1)*connections compared to O(C) in
> HashedWheelTimer when ticking.
> > Considering connections is far less then C ScheduledThreadPoolExecutor
> maybe more efficient in my opinion.
> >
> > best regards,
> >
> > Jason
>
>

Re: discuss opentracing

[Huxing Zhang]

Hi,

Welcome to the community!
There is no content in your email, would you please describe more of
what you want to discuss?

On Wed, Jan 23, 2019 at 3:25 PM Ma Xiaoguang  wrote:

-- 
Best Regards！
Huxing

Re: [ANN] Welcome new committer: Taosheng Wei

[Xin Wang]

Congratulations!

jun liu  于2019年1月24日周四 上午10:22写道：

> Hi, Taosheng
>
> Congratulations.
>
> Jun
>
> > On Jan 23, 2019, at 2:47 PM, Taosheng, Wei 
> wrote:
> >
> > Hi community,
> > I am honored to become part of Apache Dubbo community.
> > My name is Taosheng Wei, I am in Beijing. I am a server software
> engineer, working in a financial technology corporation focusing fund
> clearing of online pay.
> > I will keep contributing to the community. Let’s do our best to make
> Apache Dubbo community better and better.
> >
> >
> > Best regards,
> > Taosheng
> >
> >
> >
> >
> >
> > -- Original --
> > From: Huxing Zhang 
> > Date: Wed,Jan 23,2019 2:07 PM
> > To: dev 
> > Subject: Re: [ANN] Welcome new committer: Taosheng Wei
> >
> >
> >
> > Hi Community,
> >
> > On behalf of the Dubbo PPMC, I am pleased to announce that Taosheng Wei,
> > a.k.a. tswstarplanet[1], has been voted in as a new Dubbo committer.
> >
> > Please join me to say congratulations to him!
> >
> > Taosheng, would you please briefly introduce yourself to the community?
> >
> > [1] https://github.com/tswstarplanet
> >
> > --
> > Best Regards！
> > Huxing
>
>

Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should start it ASAP

[Taosheng, Wei]

Lan,
Yes, I think http2 and some new protocols such as rsocket can be considered.
I will spend some time to study this issue.


Warm regards,
Taosheng 




-- Original --
From: Ian Luo 
Date: Thu,Jan 24,2019 9:58 AM
To: dev 
Subject: Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should 
start it ASAP



Taosheng,

In this scenario, it looks like we should use http2 to transport the
payload, what do you think?

Thanks,
-Ian.

On Wed, Jan 23, 2019 at 10:35 PM Taosheng Wei 
wrote:

> I think we can find a binary protocol with strong potential to be a public
> application protocol like http, and extend it with security function. Or if
> there aren't such suitable protocols, we can try to formulate a new
> protocol. Then make Dubbo support it.
> In my opinion, this way may not only solve the security problems, but also
> solve the cross-language RPC with Dubbo.
>
> zhi_guang_...@163.com  ??2019??1??23?? 
> 5:47??
>
> > I have a similar Question as this mail:
> > Is Dubbo designed for use on internet?
> > I have just join a company last year and our business is all around the
> > world.
> > So we have servers on US and ASIA and EU.
> > In this condition we use dubbo on internet and keep security by security
> > rules that only allow the servers connect to each other.
> >
> > I think this is not a  pretty useage of dubbo??but I cann't find Strong
> > evidences to change the situation.
> >
> > Can any one help me to answer this questions? Thanks a lot.
> >
> >
> >
> > --
> > 
> >
> >
> > *From:* Yuhao Bi 
> > *Date:* 2019-01-22 22:55
> > *To:* dev 
> > *Subject:* Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really
> > should start it ASAP
> > Hi lan and community,
> >
> > Although I have already heard "Dubbo" a few years ago,
> > but I just started to learn dubbo after the meetup last year in Chengdu
> > after it became the Apache Dubbo.
> > Maybe I'm not such that familiar with the underlying details, but after
> > the continuous participated
> > I feel like a part of the community, and free to share my opinion.
> >
> > So, here is my question and also consider it my suggestion:
> > Should we care more about Security? How can we prevent from unauthorized
> > remote call?
> > - Should we support Authentication and Authorization
> > - Should we add Spring Security or Active Directory Service support at
> the
> > framework level
> >
> > Thanks,
> > Yuhao
> >
> >
> > jun liu  ??2019??1??22?? 5:50??
> >
> > > > I think the online integration test and performance test environment
> > > should
> > > > be set up for the new features.
> > >
> > > Agree!  We should start as soon as possible, from 2.7.x.
> > >
> > > Jun
> > >
> > > > On Jan 22, 2019, at 5:43 PM, Xin Wang 
> > wrote:
> > > >
> > > > I think the online integration test and performance test environment
> > > should
> > > > be set up for the new features.
> > > >
> > > > Ian Luo  ??2019??1??22?? 3:04??
> > > >
> > > >> Yuhao, good idea.
> > > >>
> > > >> BTW, do you have any thought on what Dubbo 3.0 should be?
> > > >>
> > > >> Thanks,
> > > >> -Ian.
> > > >>
> > > >>
> > > >> On Tue, Jan 22, 2019 at 2:39 PM Yuhao Bi  wrote:
> > > >>
> > > >>> Once we have decided what to do in the next.
> > > >>> Should we have a website page to publish it? e.g. [1]
> > > >>>
> > > >>> [1]. https://phoenix.apache.org/roadmap.html
> > > >>>
> > > >>> yuneng xie  ??2019??1??22?? 2:25??
> > > >>>
> > >  Hi Ian Luo,
> > > 
> > >  OK, i'd start to work on it soon.
> > > 
> > >  Ian Luo  ??2019??1??17?? 2:01??
> > > 
> > > > Hi Yuneng,
> > > >
> > > > Sounds interesting. I am especially interested in reactive
> > > >> programming
> > > > support. Pls. go ahead to try implement it on 3.x branch.
> > > >
> > > > Thanks,
> > > > -Ian.
> > > >
> > > > On Thu, Jan 17, 2019 at 11:03 AM yuneng xie  >
> > > >>> wrote:
> > > >
> > > >> Hi folks,
> > > >>
> > > >> I agreed with Ian Luo on the improvement list. I also got some
> > idea
> > > >>> in
> > >  my
> > > >> mind.  I'd just share with you two points below in detail which
> > i'm
> > >  most
> > > >> interested in right now.
> > > >>
> > > >> 1. Upgrade  the core abstraction "Invoker", which works in sync
> > > >> mode,
> > >  to
> > > > an
> > > >> abstraction works in async mode. then we can construct
> > > >> InvocationChain/FilterChain that works in async mode.  A core
> > >  abstraction
> > > >> works in async mode would simplify the sync/async logic. We  no
> > > >>> longer
> > > > need
> > > >> to repeat the logic about sync-mode/async-mode in each
> > > >>> ProtocolInvoker.
> > > >> ProtocolInvoker could concentrate on async logic and we could
> > > >> handle
> > > >> sync-mode invoke all in once by wrapping the
> 

Re: [Discuss] The Timer Design in Dubbo from 2.6 to 2.7

[Jason Joo]

hi, moe

This is the main differences:

ScheduledThreadPoolExecutor

O(log N) for adding new task
O(1) per each timer tick (but tick per each task, so N overall)
O(log N) cancelling the task
lock per each tick/task
HashedWheelTimer

O(1) adding new task
O(m) per each timer tick (m ~ N/C where C > 512 approx), so ~C ticks overall
O(m) for cancelling a task
lock per bucket of tasks (on each tick)


best regards,

Jason

> On Jan 24, 2019, at 10:09, 徐靖峰  wrote:
> 
> Hi, Jason，a nice opinion.
> 
> I have noticed that this issue[1] in Github encourage  the change from 
> Schedule to HashedWheelTimer, but didn’t give a vert detailed reason.
> 
> Is HashedWheelTimer really an unquestionable choice?
> 
> [1] https://github.com/apache/incubator-dubbo/issues/1371 
> 
> 
>> 在 2019年1月24日，上午9:53，Jason Joo  写道：
>> 
>> Maybe because the main scenario dubbo faces is persistent connection. 
>> For persistent connections the most frequent thing is ticking.
>> 
>> ScheduledThreadPoolExecutor is O(1)*connections compared to O(C) in 
>> HashedWheelTimer when ticking.
>> Considering connections is far less then C ScheduledThreadPoolExecutor maybe 
>> more efficient in my opinion.
>> 
>> best regards,
>> 
>> Jason
> 

Re: [Discuss] The Timer Design in Dubbo from 2.6 to 2.7

[Ian Luo]

In my opinion, it's perfectly fine to use HashedWheelTimer.

-Ian.

On Thu, Jan 24, 2019 at 10:09 AM 徐靖峰  wrote:

> Hi, Jason，a nice opinion.
>
> I have noticed that this issue[1] in Github encourage  the change from
> Schedule to HashedWheelTimer, but didn’t give a vert detailed reason.
>
> Is HashedWheelTimer really an unquestionable choice?
>
> [1] https://github.com/apache/incubator-dubbo/issues/1371 <
> https://github.com/apache/incubator-dubbo/issues/1371>
>
> > 在 2019年1月24日，上午9:53，Jason Joo  写道：
> >
> > Maybe because the main scenario dubbo faces is persistent connection.
> > For persistent connections the most frequent thing is ticking.
> >
> > ScheduledThreadPoolExecutor is O(1)*connections compared to O(C) in
> HashedWheelTimer when ticking.
> > Considering connections is far less then C ScheduledThreadPoolExecutor
> maybe more efficient in my opinion.
> >
> > best regards,
> >
> > Jason
>
>

Re: [ANN] Welcome new committer: Taosheng Wei

[jun liu]

Hi, Taosheng

Congratulations.

Jun

> On Jan 23, 2019, at 2:47 PM, Taosheng, Wei  wrote:
> 
> Hi community,
> I am honored to become part of Apache Dubbo community.
> My name is Taosheng Wei, I am in Beijing. I am a server software engineer, 
> working in a financial technology corporation focusing fund clearing of 
> online pay.
> I will keep contributing to the community. Let’s do our best to make Apache 
> Dubbo community better and better.
> 
> 
> Best regards,
> Taosheng 
> 
> 
> 
> 
> 
> -- Original --
> From: Huxing Zhang 
> Date: Wed,Jan 23,2019 2:07 PM
> To: dev 
> Subject: Re: [ANN] Welcome new committer: Taosheng Wei
> 
> 
> 
> Hi Community,
> 
> On behalf of the Dubbo PPMC, I am pleased to announce that Taosheng Wei,
> a.k.a. tswstarplanet[1], has been voted in as a new Dubbo committer.
> 
> Please join me to say congratulations to him!
> 
> Taosheng, would you please briefly introduce yourself to the community?
> 
> [1] https://github.com/tswstarplanet
> 
> -- 
> Best Regards！
> Huxing

Re: [Discuss] The Timer Design in Dubbo from 2.6 to 2.7

[徐靖峰]

Hi, Jason，a nice opinion.

I have noticed that this issue[1] in Github encourage  the change from Schedule 
to HashedWheelTimer, but didn’t give a vert detailed reason.

Is HashedWheelTimer really an unquestionable choice?

[1] https://github.com/apache/incubator-dubbo/issues/1371 


> 在 2019年1月24日，上午9:53，Jason Joo  写道：
> 
> Maybe because the main scenario dubbo faces is persistent connection. 
> For persistent connections the most frequent thing is ticking.
> 
> ScheduledThreadPoolExecutor is O(1)*connections compared to O(C) in 
> HashedWheelTimer when ticking.
> Considering connections is far less then C ScheduledThreadPoolExecutor maybe 
> more efficient in my opinion.
> 
> best regards,
> 
> Jason

Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should start it ASAP

[jun liu]

Hi Zhiguang,

> In this condition we use dubbo on internet and keep security by security 
> rules that only allow the servers connect to each other.

I want to know how do you apply the security rules to Dubbo. Can you provide 
more detail on this?

Jun

> On Jan 23, 2019, at 5:47 PM, zhi_guang_...@163.com wrote:
> 
> I have a similar Question as this mail:
> Is Dubbo designed for use on internet?
> I have just join a company last year and our business is all around the world.
> So we have servers on US and ASIA and EU.
> In this condition we use dubbo on internet and keep security by security 
> rules that only allow the servers connect to each other.
> 
> I think this is not a  pretty useage of dubbo，but I cann't find Strong 
> evidences to change the situation.
> 
> Can any one help me to answer this questions? Thanks a lot.
> 
> 
> 
> 您的朋友：刘志广
>  
> From: Yuhao Bi 
> Date: 2019-01-22 22:55
> To: dev 
> Subject: Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should 
> start it ASAP
> Hi lan and community,
>  
> Although I have already heard "Dubbo" a few years ago,
> but I just started to learn dubbo after the meetup last year in Chengdu
> after it became the Apache Dubbo.
> Maybe I'm not such that familiar with the underlying details, but after
> the continuous participated
> I feel like a part of the community, and free to share my opinion.
>  
> So, here is my question and also consider it my suggestion:
> Should we care more about Security? How can we prevent from unauthorized
> remote call?
> - Should we support Authentication and Authorization
> - Should we add Spring Security or Active Directory Service support at the
> framework level
>  
> Thanks,
> Yuhao
>  
>  
> jun liu  于2019年1月22日周二 下午5:50写道：
>  
> > > I think the online integration test and performance test environment
> > should
> > > be set up for the new features.
> >
> > Agree!  We should start as soon as possible, from 2.7.x.
> >
> > Jun
> >
> > > On Jan 22, 2019, at 5:43 PM, Xin Wang  wrote:
> > >
> > > I think the online integration test and performance test environment
> > should
> > > be set up for the new features.
> > >
> > > Ian Luo  于2019年1月22日周二 下午3:04写道：
> > >
> > >> Yuhao, good idea.
> > >>
> > >> BTW, do you have any thought on what Dubbo 3.0 should be?
> > >>
> > >> Thanks,
> > >> -Ian.
> > >>
> > >>
> > >> On Tue, Jan 22, 2019 at 2:39 PM Yuhao Bi  wrote:
> > >>
> > >>> Once we have decided what to do in the next.
> > >>> Should we have a website page to publish it? e.g. [1]
> > >>>
> > >>> [1]. https://phoenix.apache.org/roadmap.html
> > >>>
> > >>> yuneng xie  于2019年1月22日周二 下午2:25写道：
> > >>>
> >  Hi Ian Luo,
> > 
> >  OK, i'd start to work on it soon.
> > 
> >  Ian Luo  于2019年1月17日周四 下午2:01写道：
> > 
> > > Hi Yuneng,
> > >
> > > Sounds interesting. I am especially interested in reactive
> > >> programming
> > > support. Pls. go ahead to try implement it on 3.x branch.
> > >
> > > Thanks,
> > > -Ian.
> > >
> > > On Thu, Jan 17, 2019 at 11:03 AM yuneng xie 
> > >>> wrote:
> > >
> > >> Hi folks,
> > >>
> > >> I agreed with Ian Luo on the improvement list. I also got some idea
> > >>> in
> >  my
> > >> mind.  I'd just share with you two points below in detail which i'm
> >  most
> > >> interested in right now.
> > >>
> > >> 1. Upgrade  the core abstraction "Invoker", which works in sync
> > >> mode,
> >  to
> > > an
> > >> abstraction works in async mode. then we can construct
> > >> InvocationChain/FilterChain that works in async mode.  A core
> >  abstraction
> > >> works in async mode would simplify the sync/async logic. We  no
> > >>> longer
> > > need
> > >> to repeat the logic about sync-mode/async-mode in each
> > >>> ProtocolInvoker.
> > >> ProtocolInvoker could concentrate on async logic and we could
> > >> handle
> > >> sync-mode invoke all in once by wrapping the AsyncInvocationChain
> > >>> into
> >  a
> > >> SyncInvocationChain.
> > >>
> > >> 2. Support using stream-value (Fowable, Flux...)  as
> > >>> param/returnType.
> > >> really a nice feature.
> > >>
> > >> Please let me known your opinion on my points. I'm also glad to
> > >> just
> >  give
> > >> it a try and raise a pr.
> > >>
> > >>
> > >>
> > >> Ian Luo  于2019年1月10日周四 下午6:00写道：
> > >>
> > >>> Hi folks,
> > >>>
> > >>> Finally we managed to ramp down version 2.7.0 development, and
> > > hopefully
> > >> we
> > >>> can start the vote in the early of the next week. But the main
> >  purpose
> > > of
> > >>> this email is not a release announcement. Instead, since we now
> > >>> have
> > >>> bandwidth, let's consider and discuss what we should focus out
> > >> from
> > > many
> > >>> stuff we want to do. For example, we may focus more on issue and

Re: Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should start it ASAP

[Ian Luo]

Taosheng,

In this scenario, it looks like we should use http2 to transport the
payload, what do you think?

Thanks,
-Ian.

On Wed, Jan 23, 2019 at 10:35 PM Taosheng Wei 
wrote:

> I think we can find a binary protocol with strong potential to be a public
> application protocol like http, and extend it with security function. Or if
> there aren't such suitable protocols, we can try to formulate a new
> protocol. Then make Dubbo support it.
> In my opinion, this way may not only solve the security problems, but also
> solve the cross-language RPC with Dubbo.
>
> zhi_guang_...@163.com  于2019年1月23日周三 下午5:47写道：
>
> > I have a similar Question as this mail:
> > Is Dubbo designed for use on internet?
> > I have just join a company last year and our business is all around the
> > world.
> > So we have servers on US and ASIA and EU.
> > In this condition we use dubbo on internet and keep security by security
> > rules that only allow the servers connect to each other.
> >
> > I think this is not a  pretty useage of dubbo，but I cann't find Strong
> > evidences to change the situation.
> >
> > Can any one help me to answer this questions? Thanks a lot.
> >
> >
> >
> > --
> > 您的朋友：刘志广
> >
> >
> > *From:* Yuhao Bi 
> > *Date:* 2019-01-22 22:55
> > *To:* dev 
> > *Subject:* Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really
> > should start it ASAP
> > Hi lan and community,
> >
> > Although I have already heard "Dubbo" a few years ago,
> > but I just started to learn dubbo after the meetup last year in Chengdu
> > after it became the Apache Dubbo.
> > Maybe I'm not such that familiar with the underlying details, but after
> > the continuous participated
> > I feel like a part of the community, and free to share my opinion.
> >
> > So, here is my question and also consider it my suggestion:
> > Should we care more about Security? How can we prevent from unauthorized
> > remote call?
> > - Should we support Authentication and Authorization
> > - Should we add Spring Security or Active Directory Service support at
> the
> > framework level
> >
> > Thanks,
> > Yuhao
> >
> >
> > jun liu  于2019年1月22日周二 下午5:50写道：
> >
> > > > I think the online integration test and performance test environment
> > > should
> > > > be set up for the new features.
> > >
> > > Agree!  We should start as soon as possible, from 2.7.x.
> > >
> > > Jun
> > >
> > > > On Jan 22, 2019, at 5:43 PM, Xin Wang 
> > wrote:
> > > >
> > > > I think the online integration test and performance test environment
> > > should
> > > > be set up for the new features.
> > > >
> > > > Ian Luo  于2019年1月22日周二 下午3:04写道：
> > > >
> > > >> Yuhao, good idea.
> > > >>
> > > >> BTW, do you have any thought on what Dubbo 3.0 should be?
> > > >>
> > > >> Thanks,
> > > >> -Ian.
> > > >>
> > > >>
> > > >> On Tue, Jan 22, 2019 at 2:39 PM Yuhao Bi  wrote:
> > > >>
> > > >>> Once we have decided what to do in the next.
> > > >>> Should we have a website page to publish it? e.g. [1]
> > > >>>
> > > >>> [1]. https://phoenix.apache.org/roadmap.html
> > > >>>
> > > >>> yuneng xie  于2019年1月22日周二 下午2:25写道：
> > > >>>
> > >  Hi Ian Luo,
> > > 
> > >  OK, i'd start to work on it soon.
> > > 
> > >  Ian Luo  于2019年1月17日周四 下午2:01写道：
> > > 
> > > > Hi Yuneng,
> > > >
> > > > Sounds interesting. I am especially interested in reactive
> > > >> programming
> > > > support. Pls. go ahead to try implement it on 3.x branch.
> > > >
> > > > Thanks,
> > > > -Ian.
> > > >
> > > > On Thu, Jan 17, 2019 at 11:03 AM yuneng xie  >
> > > >>> wrote:
> > > >
> > > >> Hi folks,
> > > >>
> > > >> I agreed with Ian Luo on the improvement list. I also got some
> > idea
> > > >>> in
> > >  my
> > > >> mind.  I'd just share with you two points below in detail which
> > i'm
> > >  most
> > > >> interested in right now.
> > > >>
> > > >> 1. Upgrade  the core abstraction "Invoker", which works in sync
> > > >> mode,
> > >  to
> > > > an
> > > >> abstraction works in async mode. then we can construct
> > > >> InvocationChain/FilterChain that works in async mode.  A core
> > >  abstraction
> > > >> works in async mode would simplify the sync/async logic. We  no
> > > >>> longer
> > > > need
> > > >> to repeat the logic about sync-mode/async-mode in each
> > > >>> ProtocolInvoker.
> > > >> ProtocolInvoker could concentrate on async logic and we could
> > > >> handle
> > > >> sync-mode invoke all in once by wrapping the
> AsyncInvocationChain
> > > >>> into
> > >  a
> > > >> SyncInvocationChain.
> > > >>
> > > >> 2. Support using stream-value (Fowable, Flux...)  as
> > > >>> param/returnType.
> > > >> really a nice feature.
> > > >>
> > > >> Please let me known your opinion on my points. I'm also glad to
> > > >> just
> > >  give
> > > >> it a try and raise a pr.
> > > >>
> > > >>
> > > >>
> > > >> 

Re: [Discuss] The Timer Design in Dubbo from 2.6 to 2.7

[Jason Joo]

Maybe because the main scenario dubbo faces is persistent connection. 
For persistent connections the most frequent thing is ticking.

ScheduledThreadPoolExecutor is O(1)*connections compared to O(C) in 
HashedWheelTimer when ticking.
Considering connections is far less then C ScheduledThreadPoolExecutor maybe 
more efficient in my opinion.

best regards,

Jason

> On Jan 24, 2019, at 07:05, 华 钟明  wrote:
> 
> Thank you for your question, your question has been placed in the issue, 
> https://github.com/apache/incubator-dubbo/issues/3324
> please continue to pay attention
> Best Regards！
> Zhongming Hua
> 
> 
> 在 2019/1/24 上午12:31，“kirito@foxmail.com” 写入:
> 
>Hi Folks:
> 
>最近在研究 Dubbo 2.7 代码时，我发现了一个有意思的改动，Dubbo 2.6 中大量使用了 
> ScheduledThreadPoolExecutor，例如实现定时发送心跳，开启定时器用于判断异步请求超时等场景，在 Dubbo 2.7 之中替换为了由 
> Netty 实现的 HashedWheelTimer。
> 
>我对这一改动比较好奇，于是对定时器的实现做了一些调研，探讨目的是想为 2.7 选用一个最合适的定时器实现。
> 
>JDK 的 Timer 存在设计问题，不予讨论，我想主要对比 HashedWheelTimer 和 
> ScheduledThreadPoolExecutor 的区别。
> 
>Netty 在 3.x 中有大量使用 HashedWheelTimer，但是在 4.1 中，我们可以发现，Netty 保留了 
> HashedWheelTimer，但在其源码中并未使用它，而是选择了 ScheduledThreadPoolExecutor，在 Stack 
> Overflow 
> 中也有人提出这样的疑问：https://stackoverflow.com/questions/867621/efficient-timer-algorithm。
> 
>Netty 提供的 HashedWheelTimer 正如其 java doc 中所言：A  Timer optimized for 
> approximated I/O timeout scheduling. 
> 是适用于固定场景的，如果有深入研究过时间轮算法，会发现，其并没有实现多级时间轮，时间轮算法可以参考这篇论文：http://www.cs.columbia.edu/~nahum/w6998/papers/sosp87-timing-wheels.pdf
>  
> 
>我并没有找到 2.7 有关于这个改动的邮件，不太清楚去除 ScheduledThreadPoolExecutor, 使用 
> HashedWheelTimer 的原因，不知道我的检查是否有所遗漏。
> 
>下面是四个讨论点，索引一下，方便大家讨论：
> 
>1. 2.7 使用 Netty 的 HashedWheelTimer 是为了解决什么现有问题？
>2. 使用 ScheduledThreadPoolExecutor 可以更好的控制多线程执行定时任务（虽然现在的 HashWheelTimer 
> 也可以做到），尽量保持了和 2.6 的风格一致。
>3. Netty4.1 没有使用 HashedWheelTimer，我没有搜索到相关的原因，但我觉得 Netty 
> 这款优秀的框架必然考虑到了什么，希望得到大家的讨论。由于 Netty 的这一点改动，我更倾向于在 Dubbo 中也使用 
> ScheduledThreadPoolExecutor 
>4. 在心跳这样的场景，我们可以把定时器交给 netty 的 eventLoop 去做 
> Schedule，这样并不是耦合，可以做成可配置的项来选择性的重载，可以保证 Timer 线程和请求线程的线程安全（这一点是参考了 
> IdleStateHandler 的设计）。在 Dubbo 2.7 中，Timer reput 的逻辑耦合在了抽象类中，这样导致了 Timer 
> 并不具备很高的重用性。
>5. HashedWheelTimer 和 ScheduledThreadPoolExecutor 分别适用的场景
> 
>期待大家的讨论
> 
>Recently, when I was researching Dubbo 2.7 code, I found an interesting 
> change. Dubbo 2.6 used the ScheduledThreadPoolExecutor extensively. For 
> example, Dubbo implemented a timed heartbeat and started the timer to judge 
> the asynchronous request timeout. It is replaced in Dubbo 2.7 using 
> HashedWheelTimer implemented by Netty.
> 
>I was curious about this change, so I did some research on the 
> implementation of the timer. The purpose of the discussion was to choose the 
> most suitable timer for 2.7.
> 
>JDK's Timer has design issues that is no use to be discussed. I want to 
> compare the differences between HashedWheelTimer and 
> ScheduledThreadPoolExecutor.
> 
>Netty has a lot of use of HashedWheelTimer in 3.x, but in 4.1, we can find 
> that Netty retains HashedWheelTimer, but it is not used in its source code, 
> but chose ScheduledThreadPoolExecutor, which was also proposed in Stack 
> Overflow. Question: 
> https://stackoverflow.com/questions/867621/efficient-timer-algorithm.
> 
>The HashedWheelTimer provided by Netty is as described in its java doc: A 
> Timer optimized for approximated I/O timeout scheduling. It is suitable for 
> fixed scenes. If you have studied the time wheel algorithm in depth, you will 
> find that it does not implement multi-level time wheel. The time wheel 
> algorithm can refer to this paper: 
> http://www.cs.columbia.edu/~nahum/w6998/papers/sosp87-timing-wheels.pdf
> 
>I didn't find the 2.7 email about this change. I don't know why I removed 
> the ScheduledThreadPoolExecutor and used HashedWheelTimer. I don't know if my 
> check is missing.
> 
>Here are four discussion points, indexing, for your convenience:
> 
>1. 2.7 Is Netty's HashedWheelTimer used to solve any existing problems?
>2. Use ScheduledThreadPoolExecutor to better control multi-threaded 
> execution timing tasks (although HashWheelTimer can do it now), and try to 
> keep the style consistent with 2.6.
>3. Netty4.1 didn't use HashedWheelTimer, I didn't search for related 
> reasons, but I think Netty's excellent framework must take into account what 
> I want, and I hope to get everyone's discussion. Due to this change in Netty, 
> I prefer to use ScheduledThreadPoolExecutor in Dubbo as well.
>4. In a scenario like heartbeat, we can pass the timer to netty's 
> eventLoop to do the Schedule. This is not a coupling. It can be made into a 
> configurable item for selective overloading. It can guarantee the thread of 
> the Timer thread and the request thread. Security (this is a reference to the 
> design of the IdleStateHandler). In Dubbo 2.7, the logic of Timer reput is 
> coupled in an abstract class, which results in a Timer that is not highly 

Re: [Discuss] The Timer Design in Dubbo from 2.6 to 2.7

[华 钟明]

Thank you for your question, your question has been placed in the issue, 
https://github.com/apache/incubator-dubbo/issues/3324
please continue to pay attention
Best Regards！
Zhongming Hua
 

在 2019/1/24 上午12:31，“kirito@foxmail.com” 写入:

Hi Folks:

最近在研究 Dubbo 2.7 代码时，我发现了一个有意思的改动，Dubbo 2.6 中大量使用了 
ScheduledThreadPoolExecutor，例如实现定时发送心跳，开启定时器用于判断异步请求超时等场景，在 Dubbo 2.7 之中替换为了由 
Netty 实现的 HashedWheelTimer。

我对这一改动比较好奇，于是对定时器的实现做了一些调研，探讨目的是想为 2.7 选用一个最合适的定时器实现。

JDK 的 Timer 存在设计问题，不予讨论，我想主要对比 HashedWheelTimer 和 
ScheduledThreadPoolExecutor 的区别。

Netty 在 3.x 中有大量使用 HashedWheelTimer，但是在 4.1 中，我们可以发现，Netty 保留了 
HashedWheelTimer，但在其源码中并未使用它，而是选择了 ScheduledThreadPoolExecutor，在 Stack Overflow 
中也有人提出这样的疑问：https://stackoverflow.com/questions/867621/efficient-timer-algorithm。

Netty 提供的 HashedWheelTimer 正如其 java doc 中所言：A  Timer optimized for 
approximated I/O timeout scheduling. 
是适用于固定场景的，如果有深入研究过时间轮算法，会发现，其并没有实现多级时间轮，时间轮算法可以参考这篇论文：http://www.cs.columbia.edu/~nahum/w6998/papers/sosp87-timing-wheels.pdf
 

我并没有找到 2.7 有关于这个改动的邮件，不太清楚去除 ScheduledThreadPoolExecutor, 使用 
HashedWheelTimer 的原因，不知道我的检查是否有所遗漏。

下面是四个讨论点，索引一下，方便大家讨论：

1. 2.7 使用 Netty 的 HashedWheelTimer 是为了解决什么现有问题？
2. 使用 ScheduledThreadPoolExecutor 可以更好的控制多线程执行定时任务（虽然现在的 HashWheelTimer 
也可以做到），尽量保持了和 2.6 的风格一致。
3. Netty4.1 没有使用 HashedWheelTimer，我没有搜索到相关的原因，但我觉得 Netty 
这款优秀的框架必然考虑到了什么，希望得到大家的讨论。由于 Netty 的这一点改动，我更倾向于在 Dubbo 中也使用 
ScheduledThreadPoolExecutor 
4. 在心跳这样的场景，我们可以把定时器交给 netty 的 eventLoop 去做 
Schedule，这样并不是耦合，可以做成可配置的项来选择性的重载，可以保证 Timer 线程和请求线程的线程安全（这一点是参考了 
IdleStateHandler 的设计）。在 Dubbo 2.7 中，Timer reput 的逻辑耦合在了抽象类中，这样导致了 Timer 
并不具备很高的重用性。
5. HashedWheelTimer 和 ScheduledThreadPoolExecutor 分别适用的场景

期待大家的讨论

Recently, when I was researching Dubbo 2.7 code, I found an interesting 
change. Dubbo 2.6 used the ScheduledThreadPoolExecutor extensively. For 
example, Dubbo implemented a timed heartbeat and started the timer to judge the 
asynchronous request timeout. It is replaced in Dubbo 2.7 using 
HashedWheelTimer implemented by Netty.

I was curious about this change, so I did some research on the 
implementation of the timer. The purpose of the discussion was to choose the 
most suitable timer for 2.7.

JDK's Timer has design issues that is no use to be discussed. I want to 
compare the differences between HashedWheelTimer and 
ScheduledThreadPoolExecutor.

Netty has a lot of use of HashedWheelTimer in 3.x, but in 4.1, we can find 
that Netty retains HashedWheelTimer, but it is not used in its source code, but 
chose ScheduledThreadPoolExecutor, which was also proposed in Stack Overflow. 
Question: https://stackoverflow.com/questions/867621/efficient-timer-algorithm.

The HashedWheelTimer provided by Netty is as described in its java doc: A 
Timer optimized for approximated I/O timeout scheduling. It is suitable for 
fixed scenes. If you have studied the time wheel algorithm in depth, you will 
find that it does not implement multi-level time wheel. The time wheel 
algorithm can refer to this paper: 
http://www.cs.columbia.edu/~nahum/w6998/papers/sosp87-timing-wheels.pdf

I didn't find the 2.7 email about this change. I don't know why I removed 
the ScheduledThreadPoolExecutor and used HashedWheelTimer. I don't know if my 
check is missing.

Here are four discussion points, indexing, for your convenience:

1. 2.7 Is Netty's HashedWheelTimer used to solve any existing problems?
2. Use ScheduledThreadPoolExecutor to better control multi-threaded 
execution timing tasks (although HashWheelTimer can do it now), and try to keep 
the style consistent with 2.6.
3. Netty4.1 didn't use HashedWheelTimer, I didn't search for related 
reasons, but I think Netty's excellent framework must take into account what I 
want, and I hope to get everyone's discussion. Due to this change in Netty, I 
prefer to use ScheduledThreadPoolExecutor in Dubbo as well.
4. In a scenario like heartbeat, we can pass the timer to netty's eventLoop 
to do the Schedule. This is not a coupling. It can be made into a configurable 
item for selective overloading. It can guarantee the thread of the Timer thread 
and the request thread. Security (this is a reference to the design of the 
IdleStateHandler). In Dubbo 2.7, the logic of Timer reput is coupled in an 
abstract class, which results in a Timer that is not highly reusable.
5. The scenarios for HashedWheelTimer and ScheduledThreadPoolExecutor 
respectively

Look forward to your discussions.

Re: Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should start it ASAP

[Taosheng Wei]

I think we can find a binary protocol with strong potential to be a public
application protocol like http, and extend it with security function. Or if
there aren't such suitable protocols, we can try to formulate a new
protocol. Then make Dubbo support it.
In my opinion, this way may not only solve the security problems, but also
solve the cross-language RPC with Dubbo.

zhi_guang_...@163.com  于2019年1月23日周三 下午5:47写道：

> I have a similar Question as this mail:
> Is Dubbo designed for use on internet?
> I have just join a company last year and our business is all around the
> world.
> So we have servers on US and ASIA and EU.
> In this condition we use dubbo on internet and keep security by security
> rules that only allow the servers connect to each other.
>
> I think this is not a  pretty useage of dubbo，but I cann't find Strong
> evidences to change the situation.
>
> Can any one help me to answer this questions? Thanks a lot.
>
>
>
> --
> 您的朋友：刘志广
>
>
> *From:* Yuhao Bi 
> *Date:* 2019-01-22 22:55
> *To:* dev 
> *Subject:* Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really
> should start it ASAP
> Hi lan and community,
>
> Although I have already heard "Dubbo" a few years ago,
> but I just started to learn dubbo after the meetup last year in Chengdu
> after it became the Apache Dubbo.
> Maybe I'm not such that familiar with the underlying details, but after
> the continuous participated
> I feel like a part of the community, and free to share my opinion.
>
> So, here is my question and also consider it my suggestion:
> Should we care more about Security? How can we prevent from unauthorized
> remote call?
> - Should we support Authentication and Authorization
> - Should we add Spring Security or Active Directory Service support at the
> framework level
>
> Thanks,
> Yuhao
>
>
> jun liu  于2019年1月22日周二 下午5:50写道：
>
> > > I think the online integration test and performance test environment
> > should
> > > be set up for the new features.
> >
> > Agree!  We should start as soon as possible, from 2.7.x.
> >
> > Jun
> >
> > > On Jan 22, 2019, at 5:43 PM, Xin Wang 
> wrote:
> > >
> > > I think the online integration test and performance test environment
> > should
> > > be set up for the new features.
> > >
> > > Ian Luo  于2019年1月22日周二 下午3:04写道：
> > >
> > >> Yuhao, good idea.
> > >>
> > >> BTW, do you have any thought on what Dubbo 3.0 should be?
> > >>
> > >> Thanks,
> > >> -Ian.
> > >>
> > >>
> > >> On Tue, Jan 22, 2019 at 2:39 PM Yuhao Bi  wrote:
> > >>
> > >>> Once we have decided what to do in the next.
> > >>> Should we have a website page to publish it? e.g. [1]
> > >>>
> > >>> [1]. https://phoenix.apache.org/roadmap.html
> > >>>
> > >>> yuneng xie  于2019年1月22日周二 下午2:25写道：
> > >>>
> >  Hi Ian Luo,
> > 
> >  OK, i'd start to work on it soon.
> > 
> >  Ian Luo  于2019年1月17日周四 下午2:01写道：
> > 
> > > Hi Yuneng,
> > >
> > > Sounds interesting. I am especially interested in reactive
> > >> programming
> > > support. Pls. go ahead to try implement it on 3.x branch.
> > >
> > > Thanks,
> > > -Ian.
> > >
> > > On Thu, Jan 17, 2019 at 11:03 AM yuneng xie 
> > >>> wrote:
> > >
> > >> Hi folks,
> > >>
> > >> I agreed with Ian Luo on the improvement list. I also got some
> idea
> > >>> in
> >  my
> > >> mind.  I'd just share with you two points below in detail which
> i'm
> >  most
> > >> interested in right now.
> > >>
> > >> 1. Upgrade  the core abstraction "Invoker", which works in sync
> > >> mode,
> >  to
> > > an
> > >> abstraction works in async mode. then we can construct
> > >> InvocationChain/FilterChain that works in async mode.  A core
> >  abstraction
> > >> works in async mode would simplify the sync/async logic. We  no
> > >>> longer
> > > need
> > >> to repeat the logic about sync-mode/async-mode in each
> > >>> ProtocolInvoker.
> > >> ProtocolInvoker could concentrate on async logic and we could
> > >> handle
> > >> sync-mode invoke all in once by wrapping the AsyncInvocationChain
> > >>> into
> >  a
> > >> SyncInvocationChain.
> > >>
> > >> 2. Support using stream-value (Fowable, Flux...)  as
> > >>> param/returnType.
> > >> really a nice feature.
> > >>
> > >> Please let me known your opinion on my points. I'm also glad to
> > >> just
> >  give
> > >> it a try and raise a pr.
> > >>
> > >>
> > >>
> > >> Ian Luo  于2019年1月10日周四 下午6:00写道：
> > >>
> > >>> Hi folks,
> > >>>
> > >>> Finally we managed to ramp down version 2.7.0 development, and
> > > hopefully
> > >> we
> > >>> can start the vote in the early of the next week. But the main
> >  purpose
> > > of
> > >>> this email is not a release announcement. Instead, since we now
> > >>> have
> > >>> bandwidth, let's consider and discuss what we should focus out
> > >> from
> > > 

Re: Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should start it ASAP

[Ian Luo]

If the RT is acceptable between the data center, this usage is perfectly
fine.

-Ian.

On Wed, Jan 23, 2019 at 5:47 PM zhi_guang_...@163.com 
wrote:

> I have a similar Question as this mail:
> Is Dubbo designed for use on internet?
> I have just join a company last year and our business is all around the
> world.
> So we have servers on US and ASIA and EU.
> In this condition we use dubbo on internet and keep security by security
> rules that only allow the servers connect to each other.
>
> I think this is not a  pretty useage of dubbo，but I cann't find Strong
> evidences to change the situation.
>
> Can any one help me to answer this questions? Thanks a lot.
>
>
>
> --
> 您的朋友：刘志广
>
>
> *From:* Yuhao Bi 
> *Date:* 2019-01-22 22:55
> *To:* dev 
> *Subject:* Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really
> should start it ASAP
> Hi lan and community,
>
> Although I have already heard "Dubbo" a few years ago,
> but I just started to learn dubbo after the meetup last year in Chengdu
> after it became the Apache Dubbo.
> Maybe I'm not such that familiar with the underlying details, but after
> the continuous participated
> I feel like a part of the community, and free to share my opinion.
>
> So, here is my question and also consider it my suggestion:
> Should we care more about Security? How can we prevent from unauthorized
> remote call?
> - Should we support Authentication and Authorization
> - Should we add Spring Security or Active Directory Service support at the
> framework level
>
> Thanks,
> Yuhao
>
>
> jun liu  于2019年1月22日周二 下午5:50写道：
>
> > > I think the online integration test and performance test environment
> > should
> > > be set up for the new features.
> >
> > Agree!  We should start as soon as possible, from 2.7.x.
> >
> > Jun
> >
> > > On Jan 22, 2019, at 5:43 PM, Xin Wang 
> wrote:
> > >
> > > I think the online integration test and performance test environment
> > should
> > > be set up for the new features.
> > >
> > > Ian Luo  于2019年1月22日周二 下午3:04写道：
> > >
> > >> Yuhao, good idea.
> > >>
> > >> BTW, do you have any thought on what Dubbo 3.0 should be?
> > >>
> > >> Thanks,
> > >> -Ian.
> > >>
> > >>
> > >> On Tue, Jan 22, 2019 at 2:39 PM Yuhao Bi  wrote:
> > >>
> > >>> Once we have decided what to do in the next.
> > >>> Should we have a website page to publish it? e.g. [1]
> > >>>
> > >>> [1]. https://phoenix.apache.org/roadmap.html
> > >>>
> > >>> yuneng xie  于2019年1月22日周二 下午2:25写道：
> > >>>
> >  Hi Ian Luo,
> > 
> >  OK, i'd start to work on it soon.
> > 
> >  Ian Luo  于2019年1月17日周四 下午2:01写道：
> > 
> > > Hi Yuneng,
> > >
> > > Sounds interesting. I am especially interested in reactive
> > >> programming
> > > support. Pls. go ahead to try implement it on 3.x branch.
> > >
> > > Thanks,
> > > -Ian.
> > >
> > > On Thu, Jan 17, 2019 at 11:03 AM yuneng xie 
> > >>> wrote:
> > >
> > >> Hi folks,
> > >>
> > >> I agreed with Ian Luo on the improvement list. I also got some
> idea
> > >>> in
> >  my
> > >> mind.  I'd just share with you two points below in detail which
> i'm
> >  most
> > >> interested in right now.
> > >>
> > >> 1. Upgrade  the core abstraction "Invoker", which works in sync
> > >> mode,
> >  to
> > > an
> > >> abstraction works in async mode. then we can construct
> > >> InvocationChain/FilterChain that works in async mode.  A core
> >  abstraction
> > >> works in async mode would simplify the sync/async logic. We  no
> > >>> longer
> > > need
> > >> to repeat the logic about sync-mode/async-mode in each
> > >>> ProtocolInvoker.
> > >> ProtocolInvoker could concentrate on async logic and we could
> > >> handle
> > >> sync-mode invoke all in once by wrapping the AsyncInvocationChain
> > >>> into
> >  a
> > >> SyncInvocationChain.
> > >>
> > >> 2. Support using stream-value (Fowable, Flux...)  as
> > >>> param/returnType.
> > >> really a nice feature.
> > >>
> > >> Please let me known your opinion on my points. I'm also glad to
> > >> just
> >  give
> > >> it a try and raise a pr.
> > >>
> > >>
> > >>
> > >> Ian Luo  于2019年1月10日周四 下午6:00写道：
> > >>
> > >>> Hi folks,
> > >>>
> > >>> Finally we managed to ramp down version 2.7.0 development, and
> > > hopefully
> > >> we
> > >>> can start the vote in the early of the next week. But the main
> >  purpose
> > > of
> > >>> this email is not a release announcement. Instead, since we now
> > >>> have
> > >>> bandwidth, let's consider and discuss what we should focus out
> > >> from
> > > many
> > >>> stuff we want to do. For example, we may focus more on issue and
> > >>> pull
> > >>> request on GitHub, or we may plan 2.7 minor releases immediately
> >  after
> > > we
> > >>> release 2.7.0. But today I'd like to bring up one longer term
> 

Re: Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should start it ASAP

[zhi_guang_...@163.com]

I have a similar Question as this mail:
Is Dubbo designed for use on internet?
I have just join a company last year and our business is all around the world.
So we have servers on US and ASIA and EU.
In this condition we use dubbo on internet and keep security by security rules 
that only allow the servers connect to each other.

I think this is not a  pretty useage of dubbo，but I cann't find Strong 
evidences to change the situation.

Can any one help me to answer this questions? Thanks a lot.





您的朋友：刘志广
 
From: Yuhao Bi
Date: 2019-01-22 22:55
To: dev
Subject: Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should 
start it ASAP
Hi lan and community,
 
Although I have already heard "Dubbo" a few years ago,
but I just started to learn dubbo after the meetup last year in Chengdu
after it became the Apache Dubbo.
Maybe I'm not such that familiar with the underlying details, but after
the continuous participated
I feel like a part of the community, and free to share my opinion.
 
So, here is my question and also consider it my suggestion:
Should we care more about Security? How can we prevent from unauthorized
remote call?
- Should we support Authentication and Authorization
- Should we add Spring Security or Active Directory Service support at the
framework level
 
Thanks,
Yuhao
 
 
jun liu  于2019年1月22日周二 下午5:50写道：
 
> > I think the online integration test and performance test environment
> should
> > be set up for the new features.
>
> Agree!  We should start as soon as possible, from 2.7.x.
>
> Jun
>
> > On Jan 22, 2019, at 5:43 PM, Xin Wang  wrote:
> >
> > I think the online integration test and performance test environment
> should
> > be set up for the new features.
> >
> > Ian Luo  于2019年1月22日周二 下午3:04写道：
> >
> >> Yuhao, good idea.
> >>
> >> BTW, do you have any thought on what Dubbo 3.0 should be?
> >>
> >> Thanks,
> >> -Ian.
> >>
> >>
> >> On Tue, Jan 22, 2019 at 2:39 PM Yuhao Bi  wrote:
> >>
> >>> Once we have decided what to do in the next.
> >>> Should we have a website page to publish it? e.g. [1]
> >>>
> >>> [1]. https://phoenix.apache.org/roadmap.html
> >>>
> >>> yuneng xie  于2019年1月22日周二 下午2:25写道：
> >>>
>  Hi Ian Luo,
> 
>  OK, i'd start to work on it soon.
> 
>  Ian Luo  于2019年1月17日周四 下午2:01写道：
> 
> > Hi Yuneng,
> >
> > Sounds interesting. I am especially interested in reactive
> >> programming
> > support. Pls. go ahead to try implement it on 3.x branch.
> >
> > Thanks,
> > -Ian.
> >
> > On Thu, Jan 17, 2019 at 11:03 AM yuneng xie 
> >>> wrote:
> >
> >> Hi folks,
> >>
> >> I agreed with Ian Luo on the improvement list. I also got some idea
> >>> in
>  my
> >> mind.  I'd just share with you two points below in detail which i'm
>  most
> >> interested in right now.
> >>
> >> 1. Upgrade  the core abstraction "Invoker", which works in sync
> >> mode,
>  to
> > an
> >> abstraction works in async mode. then we can construct
> >> InvocationChain/FilterChain that works in async mode.  A core
>  abstraction
> >> works in async mode would simplify the sync/async logic. We  no
> >>> longer
> > need
> >> to repeat the logic about sync-mode/async-mode in each
> >>> ProtocolInvoker.
> >> ProtocolInvoker could concentrate on async logic and we could
> >> handle
> >> sync-mode invoke all in once by wrapping the AsyncInvocationChain
> >>> into
>  a
> >> SyncInvocationChain.
> >>
> >> 2. Support using stream-value (Fowable, Flux...)  as
> >>> param/returnType.
> >> really a nice feature.
> >>
> >> Please let me known your opinion on my points. I'm also glad to
> >> just
>  give
> >> it a try and raise a pr.
> >>
> >>
> >>
> >> Ian Luo  于2019年1月10日周四 下午6:00写道：
> >>
> >>> Hi folks,
> >>>
> >>> Finally we managed to ramp down version 2.7.0 development, and
> > hopefully
> >> we
> >>> can start the vote in the early of the next week. But the main
>  purpose
> > of
> >>> this email is not a release announcement. Instead, since we now
> >>> have
> >>> bandwidth, let's consider and discuss what we should focus out
> >> from
> > many
> >>> stuff we want to do. For example, we may focus more on issue and
> >>> pull
> >>> request on GitHub, or we may plan 2.7 minor releases immediately
>  after
> > we
> >>> release 2.7.0. But today I'd like to bring up one longer term
> >> plan
> > which
> >>> I'm now caring most, that is, how we define what version 3.0 is?
> >>> and
> > when
> >>> can we get start on it? In my opinion, we need to start it right
> >>> from
> >> this
> >>> moment.
> >>>
> >>> I recalled Liujie Qin (@liujieqin) initialed the discussion on
> >> the
>  same
> >>> topic [1] in July this year. I summarize his points here if you
> >> are
>  too
> >>> impatient to read through the contents 

PR raised to make multicast registry work in ipv6 environment

[jun liu]

I have just raised a PR[1] aiming to fix the long bothering issue when using 
multicast registry in an ipv6 environment. While I am not familiar enough with 
ipv6 and multicast, review comments are needed to make sure the changes can 
work fine.

Consider this one as a beginning for “Developing Experience Improvement”[2], I 
will try to post some other ones that I think are of great importance regarding 
easy use into this project.

1. https://github.com/apache/incubator-dubbo/pull/3317
2. https://github.com/apache/incubator-dubbo/projects/3

Jun

Re: [ANN] Welcome new committer: Taosheng Wei

[Jun Alpha]

Congratulations

Imteyaz Khan  于2019年1月23日周三 下午4:04写道：

> Congratulation, thank you for your contributions.
>
> On Wed, Jan 23, 2019 at 1:04 PM 华 钟明  wrote:
>
> > Congratulations, thank you for your contribution.
> >
> > Zhongming Hua
> >
> >
> >
> > 在 2019/1/23 下午3:31，“LiZhenNet” 写入:
> >
> > Congratulations
> >
> > Yuhao Bi  于2019年1月23日周三 下午2:56写道：
> >
> > > Congratulations to you and thank you for your contribution!
> > >
> > > Taosheng, Wei  于2019年1月23日周三 下午2:47写道：
> > >
> > > > Hi community,
> > > > I am honored to become part of Apache Dubbo community.
> > > > My name is Taosheng Wei, I am in Beijing. I am a server software
> > > engineer,
> > > > working in a financial technology corporation focusing fund
> > clearing of
> > > > online pay.
> > > > I will keep contributing to the community. Let’s do our best to
> > make
> > > > Apache Dubbo community better and better.
> > > >
> > > >
> > > > Best regards,
> > > > Taosheng
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -- Original --
> > > > From: Huxing Zhang 
> > > > Date: Wed,Jan 23,2019 2:07 PM
> > > > To: dev 
> > > > Subject: Re: [ANN] Welcome new committer: Taosheng Wei
> > > >
> > > >
> > > >
> > > > Hi Community,
> > > >
> > > > On behalf of the Dubbo PPMC, I am pleased to announce that
> > Taosheng Wei,
> > > > a.k.a. tswstarplanet[1], has been voted in as a new Dubbo
> > committer.
> > > >
> > > > Please join me to say congratulations to him!
> > > >
> > > > Taosheng, would you please briefly introduce yourself to the
> > community?
> > > >
> > > > [1] https://github.com/tswstarplanet
> > > >
> > > > --
> > > > Best Regards！
> > > > Huxing
> > >
> >
> >
>

Re: [ANN] Welcome new committer: Taosheng Wei

[Imteyaz Khan]

Congratulation, thank you for your contributions.

On Wed, Jan 23, 2019 at 1:04 PM 华 钟明  wrote:

> Congratulations, thank you for your contribution.
>
> Zhongming Hua
>
>
>
> 在 2019/1/23 下午3:31，“LiZhenNet” 写入:
>
> Congratulations
>
> Yuhao Bi  于2019年1月23日周三 下午2:56写道：
>
> > Congratulations to you and thank you for your contribution!
> >
> > Taosheng, Wei  于2019年1月23日周三 下午2:47写道：
> >
> > > Hi community,
> > > I am honored to become part of Apache Dubbo community.
> > > My name is Taosheng Wei, I am in Beijing. I am a server software
> > engineer,
> > > working in a financial technology corporation focusing fund
> clearing of
> > > online pay.
> > > I will keep contributing to the community. Let’s do our best to
> make
> > > Apache Dubbo community better and better.
> > >
> > >
> > > Best regards,
> > > Taosheng
> > >
> > >
> > >
> > >
> > >
> > > -- Original --
> > > From: Huxing Zhang 
> > > Date: Wed,Jan 23,2019 2:07 PM
> > > To: dev 
> > > Subject: Re: [ANN] Welcome new committer: Taosheng Wei
> > >
> > >
> > >
> > > Hi Community,
> > >
> > > On behalf of the Dubbo PPMC, I am pleased to announce that
> Taosheng Wei,
> > > a.k.a. tswstarplanet[1], has been voted in as a new Dubbo
> committer.
> > >
> > > Please join me to say congratulations to him!
> > >
> > > Taosheng, would you please briefly introduce yourself to the
> community?
> > >
> > > [1] https://github.com/tswstarplanet
> > >
> > > --
> > > Best Regards！
> > > Huxing
> >
>
>