We may do something like this:
Keep a copy of the instance/metadata information in clientside, and when
the SC is down, the client can still use the local information to visit
services.
On Wed, May 16, 2018 at 11:15 AM, Willem Jiang
wrote:
> If we treat the service center as an online service,
Sorry, replied to the wrong mail.
On Wed, May 16, 2018 at 11:35 AM, Yang Bo wrote:
> We may do something like this:
> Keep a copy of the instance/metadata information in clientside, and when
> the SC is down, the client can still use the local information to visit
> services.
>
> On Wed, May 16
We may do something like this:
Keep a copy of the instance/metadata information in clientside, and when
the SC is down, the client can still use the local information to visit
services.
On Wed, May 16, 2018 at 11:01 AM, Willem Jiang
wrote:
> Hi Wujimin
>
> Could you write some code snippet for u
If we treat the service center as an online service, it should provide 7*24
services.
But if we use the standalone service center, it could be challenge for the
service center provide 7*24 service.
How can we setup the instance refresh strategy?
We may need to provide different solution for differ
Hi Wujimin
Could you write some code snippet for using the lambda in the EventBus?
As you said earlier, the EventBus uses reflection which may cause some
performance issue.
But I don't know how the lambda can to the same thing in EventBus.
Willem Jiang
Blog: http://willemjiang.blogspot.com (Eng
i have tested dynamic lambda, very fast, almost equals direct call
so abandon interface solution at last
still use guava EventBus
if cause performance problem, then rewrite a compatible EventBus
static T createLambda(Object instance, Method instanceMethod,
Class functionalIntfCls)
throws Th
