You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dubbo.apache.org by li...@apache.org on 2020/10/21 10:11:39 UTC
[dubbo-website] 02/38: mkdocs material theme init
This is an automated email from the ASF dual-hosted git repository.
liujun pushed a commit to branch mkdocs
in repository https://gitbox.apache.org/repos/asf/dubbo-website.git
commit 66e21f0b87ae1abdda67d9b3b8f3a2c112d8a7cb
Author: ken.lj <ke...@gmail.com>
AuthorDate: Thu Aug 13 00:14:28 2020 +0800
mkdocs material theme init
---
.docsite | 0
.gitignore | 3 +-
blog/en-us/apachecon-na-2018.md | 10 -
blog/en-us/download.md | 178 --
blog/en-us/dubbo-101.md | 390 ---
blog/en-us/dubbo-annotation.md | 362 ---
...bbo-basic-usage-dubbo-consumer-configuration.md | 193 --
...bbo-basic-usage-dubbo-provider-configuration.md | 288 --
blog/en-us/dubbo-fescar.md | 227 --
blog/en-us/dubbo-generic-invoke.md | 186 --
blog/en-us/dubbo-invoke.md | 221 --
blog/en-us/dubbo-k8s.md | 142 -
blog/en-us/dubbo-loadbalance.md | 271 --
blog/en-us/dubbo-meetup-beijing-may-12th-2018.md | 16 -
blog/en-us/dubbo-meetup-chengdu.md | 25 -
blog/en-us/dubbo-meetup-hangzhou.md | 19 -
blog/en-us/dubbo-meetup-shanghai-jun-23rd-2018.md | 16 -
blog/en-us/dubbo-meetup-shenzhen.md | 15 -
blog/en-us/dubbo-new-async.md | 585 ----
blog/en-us/dubbo-protocol.md | 182 --
blog/en-us/dubbo-registry-nacos-integration.md | 487 ----
blog/en-us/dubbo-zk.md | 341 ---
blog/en-us/dubbo2-js.md | 274 --
blog/en-us/dubboAsync_client.md | 85 -
blog/en-us/dubboAsync_server.md | 98 -
blog/en-us/first-dubbo-filter.md | 212 --
blog/en-us/gsoc-2018.md | 10 -
blog/en-us/introduction-to-dubbo-qos.md | 254 --
blog/en-us/introduction-to-dubbo-spi-2.md | 407 ---
blog/en-us/introduction-to-dubbo-spi.md | 242 --
blog/en-us/pinpoint.md | 417 ---
blog/en-us/prepare-an-apache-release.md | 518 ----
blog/en-us/qcon-beijing-2018.md | 11 -
blog/en-us/sentinel-introduction-for-dubbo.md | 110 -
blog/en-us/service-test.md | 170 --
.../en-us/spring-boot-dubbo-start-stop-analysis.md | 229 --
blog/en-us/tracing-with-skywalking.md | 149 -
blog/zh-cn/2.7.5-release.md | 274 --
.../Dubbo-supporting-gRPC-HTTP2-and-protobuf.md | 726 -----
blog/zh-cn/apache-dubbo-2019-2020.md | 312 --
blog/zh-cn/apachecon-na-2018.md | 10 -
blog/zh-cn/build-new-docker-image-in-dockerhub.md | 58 -
blog/zh-cn/connect-heterogeneous-microservices.md | 290 --
blog/zh-cn/download.md | 178 --
blog/zh-cn/dubbo-101.md | 381 ---
blog/zh-cn/dubbo-27-features.md | 230 --
blog/zh-cn/dubbo-admin.md | 71 -
blog/zh-cn/dubbo-annotation-driven.md | 809 ------
blog/zh-cn/dubbo-annotation.md | 386 ---
...bbo-basic-usage-dubbo-consumer-configuration.md | 195 --
...bbo-basic-usage-dubbo-provider-configuration.md | 288 --
blog/zh-cn/dubbo-cluster-error-handling.md | 270 --
blog/zh-cn/dubbo-compatible.md | 197 --
blog/zh-cn/dubbo-consistent-hash-implementation.md | 284 --
blog/zh-cn/dubbo-context-information.md | 60 -
blog/zh-cn/dubbo-contribute-to-opensource.md | 196 --
blog/zh-cn/dubbo-copywriting-style.md | 272 --
blog/zh-cn/dubbo-echo-test.md | 93 -
blog/zh-cn/dubbo-externalized-configuration.md | 690 -----
blog/zh-cn/dubbo-fescar.md | 227 --
blog/zh-cn/dubbo-generic-invoke.md | 178 --
blog/zh-cn/dubbo-gracefully-shutdown.md | 114 -
blog/zh-cn/dubbo-heartbeat-design.md | 386 ---
blog/zh-cn/dubbo-integrate-with-hystrix.md | 207 --
blog/zh-cn/dubbo-invoke.md | 221 --
blog/zh-cn/dubbo-k8s.md | 101 -
blog/zh-cn/dubbo-loadbalance.md | 271 --
blog/zh-cn/dubbo-local-call.md | 139 -
blog/zh-cn/dubbo-meet-arthas.md | 365 ---
blog/zh-cn/dubbo-meetup-beijing-may-12th-2018.md | 17 -
blog/zh-cn/dubbo-meetup-chengdu.md | 26 -
blog/zh-cn/dubbo-meetup-hangzhou.md | 19 -
blog/zh-cn/dubbo-meetup-shanghai-jun-23rd-2018.md | 16 -
blog/zh-cn/dubbo-meetup-shenzhen.md | 15 -
blog/zh-cn/dubbo-mesh-in-thinking.md | 135 -
blog/zh-cn/dubbo-mesh-service-mesh-exploring.md | 157 -
blog/zh-cn/dubbo-network-interfaces.md | 526 ----
blog/zh-cn/dubbo-new-async.md | 462 ---
blog/zh-cn/dubbo-practice-from-guazi.md | 169 --
blog/zh-cn/dubbo-protocol.md | 205 --
blog/zh-cn/dubbo-registry-nacos-integration.md | 555 ----
blog/zh-cn/dubbo-rest.md | 845 ------
blog/zh-cn/dubbo-stub-mock.md | 313 --
blog/zh-cn/dubbo-zk.md | 346 ---
blog/zh-cn/dubbo2-js.md | 277 --
blog/zh-cn/dubboAsync_client.md | 89 -
blog/zh-cn/dubboAsync_server.md | 95 -
blog/zh-cn/first-dubbo-filter.md | 195 --
blog/zh-cn/gsoc-2018.md | 10 -
blog/zh-cn/how-to-involve-dubbo-community.md | 112 -
blog/zh-cn/introduction-to-dubbo-qos.md | 260 --
blog/zh-cn/introduction-to-dubbo-spi-2.md | 406 ---
blog/zh-cn/introduction-to-dubbo-spi.md | 231 --
blog/zh-cn/introduction-to-dubbo-url.md | 176 --
blog/zh-cn/meet-dubbo.md | 64 -
blog/zh-cn/optimization-branch-prediction.md | 140 -
blog/zh-cn/pinpoint.md | 421 ---
blog/zh-cn/prepare-an-apache-release.md | 496 ----
blog/zh-cn/qcon-beijing-2018.md | 10 -
blog/zh-cn/rpc-introduction.md | 132 -
blog/zh-cn/sentinel-introduction-for-dubbo.md | 140 -
blog/zh-cn/service-and-version.md | 195 --
blog/zh-cn/service-test.md | 157 -
.../zh-cn/spring-boot-dubbo-start-stop-analysis.md | 234 --
blog/zh-cn/test-verification.md | 92 -
blog/zh-cn/tracing-with-skywalking.md | 141 -
blog/zh-cn/use-zipkin-in-dubbo.md | 604 ----
docs/README.md | 2 -
docs/en-us/admin/README.md | 3 -
docs/en-us/admin/SUMMARY.md | 4 -
docs/en-us/admin/install/admin-console.md | 40 -
docs/en-us/admin/install/consumer-demo.md | 20 -
docs/en-us/admin/install/introduction.md | 13 -
docs/en-us/admin/install/provider-demo.md | 18 -
docs/en-us/admin/install/redis.md | 54 -
docs/en-us/admin/install/simple-monitor-center.md | 3 -
docs/en-us/admin/install/simple-registry-center.md | 1 -
docs/en-us/admin/install/zookeeper.md | 98 -
docs/en-us/admin/introduction.md | 65 -
docs/en-us/admin/ops/dubbo-ops.md | 26 -
docs/en-us/admin/ops/introduction.md | 1 -
docs/en-us/admin/ops/pinpoint.md | 411 ---
docs/en-us/admin/ops/skywalking.md | 121 -
docs/en-us/admin/serviceGovernance.md | 46 -
docs/en-us/admin/serviceSearch.md | 7 -
docs/en-us/admin/serviceTest.md | 1 -
docs/en-us/admin/sources/images/blackList.jpg | Bin 99079 -> 0 bytes
docs/en-us/admin/sources/images/check.gif | Bin 604 -> 0 bytes
docs/en-us/admin/sources/images/config.jpg | Bin 137909 -> 0 bytes
docs/en-us/admin/sources/images/detail.jpg | Bin 188392 -> 0 bytes
.../admin/sources/images/dubbo-add-config.jpg | Bin 303596 -> 0 bytes
.../en-us/admin/sources/images/dubbo-add-route.jpg | Bin 330146 -> 0 bytes
.../admin/sources/images/dubbo-applications.png | Bin 93036 -> 0 bytes
.../en-us/admin/sources/images/dubbo-consumers.jpg | Bin 274307 -> 0 bytes
.../admin/sources/images/dubbo-monitor-simple.jpg | Bin 87670 -> 0 bytes
.../en-us/admin/sources/images/dubbo-providers.jpg | Bin 272674 -> 0 bytes
docs/en-us/admin/sources/images/dubbo-search.jpg | Bin 224751 -> 0 bytes
.../admin/sources/images/pinpoint-calltree.png | Bin 655223 -> 0 bytes
docs/en-us/admin/sources/images/pinpoint-home.png | Bin 303613 -> 0 bytes
.../admin/sources/images/pinpoint-mixedview.png | Bin 434638 -> 0 bytes
docs/en-us/admin/sources/images/searchResult.png | Bin 168461 -> 0 bytes
.../admin/sources/images/skywalking-alarm.png | Bin 181739 -> 0 bytes
.../sources/images/skywalking-application.png | Bin 229539 -> 0 bytes
.../images/skywalking-application_instance.png | Bin 203651 -> 0 bytes
.../admin/sources/images/skywalking-dashboard.png | Bin 257273 -> 0 bytes
.../sources/images/skywalking-service-consumer.png | Bin 282541 -> 0 bytes
.../sources/images/skywalking-service-provider.png | Bin 366038 -> 0 bytes
.../admin/sources/images/skywalking-span-Info.png | Bin 192403 -> 0 bytes
.../admin/sources/images/skywalking-topology.png | Bin 173667 -> 0 bytes
.../admin/sources/images/skywalking-trace.png | Bin 217096 -> 0 bytes
docs/en-us/admin/sources/images/tip.png | Bin 876 -> 0 bytes
docs/en-us/admin/sources/images/warning-3.gif | Bin 569 -> 0 bytes
docs/en-us/admin/sources/images/weight.jpg | Bin 89265 -> 0 bytes
docs/en-us/dev/LICENSE | 201 --
docs/en-us/dev/README.md | 3 -
docs/en-us/dev/SPI.md | 237 --
docs/en-us/dev/SUMMARY.md | 41 -
docs/en-us/dev/TCK.md | 19 -
docs/en-us/dev/build.md | 81 -
docs/en-us/dev/checklist.md | 19 -
docs/en-us/dev/code-smell.md | 205 --
docs/en-us/dev/coding.md | 53 -
docs/en-us/dev/contract.md | 14 -
docs/en-us/dev/contribution.md | 89 -
docs/en-us/dev/design.md | 99 -
docs/en-us/dev/implementation.md | 155 -
docs/en-us/dev/impls/cache.md | 84 -
docs/en-us/dev/impls/cluster.md | 74 -
docs/en-us/dev/impls/compiler.md | 55 -
docs/en-us/dev/impls/config-center.md | 96 -
docs/en-us/dev/impls/container.md | 62 -
docs/en-us/dev/impls/dispatcher.md | 62 -
docs/en-us/dev/impls/exchanger.md | 91 -
docs/en-us/dev/impls/exporter-listener.md | 66 -
docs/en-us/dev/impls/extension-factory.md | 57 -
docs/en-us/dev/impls/filter.md | 89 -
docs/en-us/dev/impls/introduction.md | 3 -
docs/en-us/dev/impls/invoker-listener.md | 65 -
docs/en-us/dev/impls/load-balance.md | 63 -
docs/en-us/dev/impls/logger-adapter.md | 84 -
docs/en-us/dev/impls/merger.md | 60 -
docs/en-us/dev/impls/monitor.md | 75 -
docs/en-us/dev/impls/networker.md | 59 -
docs/en-us/dev/impls/page.md | 61 -
docs/en-us/dev/impls/protocol.md | 150 -
docs/en-us/dev/impls/proxy-factory.md | 65 -
docs/en-us/dev/impls/registry.md | 207 --
docs/en-us/dev/impls/remoting.md | 122 -
docs/en-us/dev/impls/router.md | 58 -
docs/en-us/dev/impls/serialize.md | 72 -
docs/en-us/dev/impls/status-checker.md | 64 -
docs/en-us/dev/impls/telnet-handler.md | 77 -
docs/en-us/dev/impls/threadpool.md | 61 -
docs/en-us/dev/impls/validation.md | 75 -
docs/en-us/dev/introduction.md | 0
docs/en-us/dev/principals/code-detail.md | 36 -
docs/en-us/dev/principals/configuration.md | 83 -
docs/en-us/dev/principals/dummy.md | 203 --
docs/en-us/dev/principals/expansibility.md | 18 -
docs/en-us/dev/principals/extension.md | 135 -
docs/en-us/dev/principals/general-knowledge.md | 68 -
docs/en-us/dev/principals/introduction.md | 3 -
docs/en-us/dev/principals/robustness.md | 83 -
docs/en-us/dev/release.md | 34 -
docs/en-us/dev/sources/images/close-expand.jpg | Bin 19287 -> 0 bytes
.../dev/sources/images/configuration-override.png | Bin 11422 -> 0 bytes
docs/en-us/dev/sources/images/ddd.jpg | Bin 19358 -> 0 bytes
docs/en-us/dev/sources/images/design-step1.png | Bin 121672 -> 0 bytes
docs/en-us/dev/sources/images/design-step2.png | Bin 141298 -> 0 bytes
docs/en-us/dev/sources/images/design-step3.png | Bin 165828 -> 0 bytes
docs/en-us/dev/sources/images/design-step4.png | Bin 240786 -> 0 bytes
docs/en-us/dev/sources/images/dubbo-export.jpg | Bin 70132 -> 0 bytes
docs/en-us/dev/sources/images/dubbo-extension.jpg | Bin 112692 -> 0 bytes
docs/en-us/dev/sources/images/dubbo-framework.jpg | Bin 219759 -> 0 bytes
docs/en-us/dev/sources/images/dubbo-modules.jpg | Bin 25411 -> 0 bytes
docs/en-us/dev/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
docs/en-us/dev/sources/images/dubbo-refer.jpg | Bin 105967 -> 0 bytes
docs/en-us/dev/sources/images/dubbo-relation.jpg | Bin 30304 -> 0 bytes
.../dev/sources/images/dubbo_protocol_header.png | Bin 74833 -> 0 bytes
docs/en-us/dev/sources/images/dubbo_rpc_export.jpg | Bin 47624 -> 0 bytes
docs/en-us/dev/sources/images/dubbo_rpc_invoke.jpg | Bin 45874 -> 0 bytes
docs/en-us/dev/sources/images/dubbo_rpc_refer.jpg | Bin 50211 -> 0 bytes
docs/en-us/dev/sources/images/event-listener.jpg | Bin 13192 -> 0 bytes
docs/en-us/dev/sources/images/filter-chain.jpg | Bin 41029 -> 0 bytes
docs/en-us/dev/sources/images/mix-api-spi.jpg | Bin 17004 -> 0 bytes
docs/en-us/dev/sources/images/open-expand.jpg | Bin 10549 -> 0 bytes
docs/en-us/dev/sources/images/seperate-api-spi.jpg | Bin 23683 -> 0 bytes
.../committer-guide/apache-dubbo-page_dev.md | 33 -
.../committer-guide/label-an-issue-guide_dev.md | 29 -
.../committer-guide/new-committer-guide_dev.md | 95 -
.../committer-guide/release-guide_dev.md | 500 ----
.../committer-guide/website-guide_dev.md | 4 -
.../contributor-guide/become-a-committer_dev.md | 15 -
.../contributor-guide/cla-signing-guide_dev.md | 25 -
.../contributor-guide/dubbo-extension-guide_dev.md | 37 -
.../mailing-list-subscription-guide_dev.md | 80 -
.../contributor-guide/new-contributor-guide_dev.md | 62 -
.../reporting-security-issues_dev.md | 21 -
.../software-donation-guide_dev.md | 106 -
.../contributor-guide/test-coverage-guide_dev.md | 16 -
docs/en-us/developers/developers_dev.md | 57 -
docs/en-us/developers/guide_dev.md | 76 -
docs/en-us/developers/user-guide/faq_dev.md | 27 -
docs/en-us/user/LICENSE | 201 --
docs/en-us/user/README.md | 3 -
docs/en-us/user/SUMMARY.md | 94 -
docs/en-us/user/benchmark-tool.md | 34 -
docs/en-us/user/best-practice.md | 63 -
docs/en-us/user/capacity-plan.md | 17 -
docs/en-us/user/configuration/annotation.md | 94 -
docs/en-us/user/configuration/api.md | 119 -
.../configuration/configuration-load-process.md | 180 --
docs/en-us/user/configuration/index.md | 1 -
docs/en-us/user/configuration/properties.md | 43 -
docs/en-us/user/configuration/xml.md | 77 -
docs/en-us/user/coveragence.md | 24 -
docs/en-us/user/demos/accesslog.md | 57 -
docs/en-us/user/demos/async-call-deprecated.md | 59 -
docs/en-us/user/demos/async-call.md | 59 -
docs/en-us/user/demos/async-execute-on-provider.md | 90 -
docs/en-us/user/demos/attachment.md | 27 -
docs/en-us/user/demos/callback-parameter.md | 110 -
docs/en-us/user/demos/concurrency-control.md | 60 -
docs/en-us/user/demos/config-connections.md | 30 -
docs/en-us/user/demos/config-rule-deprecated.md | 47 -
docs/en-us/user/demos/config-rule.md | 47 -
docs/en-us/user/demos/context.md | 39 -
docs/en-us/user/demos/delay-publish.md | 50 -
docs/en-us/user/demos/distributed-transaction.md | 7 -
docs/en-us/user/demos/dump.md | 19 -
docs/en-us/user/demos/echo-service.md | 25 -
docs/en-us/user/demos/events-notify.md | 95 -
docs/en-us/user/demos/explicit-target.md | 37 -
docs/en-us/user/demos/fault-tolerent-strategy.md | 75 -
docs/en-us/user/demos/generic-reference.md | 97 -
docs/en-us/user/demos/generic-service.md | 45 -
docs/en-us/user/demos/graceful-shutdown.md | 30 -
docs/en-us/user/demos/group-merger.md | 54 -
docs/en-us/user/demos/hostname-binding.md | 58 -
docs/en-us/user/demos/index.md | 1 -
docs/en-us/user/demos/introduction.md | 2 -
docs/en-us/user/demos/lazy-connect.md | 9 -
docs/en-us/user/demos/loadbalance.md | 64 -
docs/en-us/user/demos/local-call.md | 48 -
docs/en-us/user/demos/local-mock.md | 100 -
docs/en-us/user/demos/local-stub.md | 47 -
docs/en-us/user/demos/logger-strategy.md | 23 -
docs/en-us/user/demos/multi-protocols.md | 45 -
docs/en-us/user/demos/multi-registry.md | 83 -
docs/en-us/user/demos/multi-versions.md | 42 -
docs/en-us/user/demos/netty4.md | 35 -
docs/en-us/user/demos/parameter-validation.md | 183 --
docs/en-us/user/demos/preflight-check.md | 56 -
docs/en-us/user/demos/reference-config-cache.md | 38 -
docs/en-us/user/demos/registry-only.md | 19 -
docs/en-us/user/demos/result-cache.md | 28 -
docs/en-us/user/demos/routing-rule.md | 193 --
docs/en-us/user/demos/serialization.md | 77 -
docs/en-us/user/demos/service-container.md | 61 -
docs/en-us/user/demos/service-downgrade.md | 19 -
docs/en-us/user/demos/service-group.md | 27 -
docs/en-us/user/demos/static-service.md | 27 -
docs/en-us/user/demos/stickiness.md | 17 -
docs/en-us/user/demos/subscribe-only.md | 19 -
docs/en-us/user/demos/thread-model.md | 34 -
docs/en-us/user/demos/token-authorization.md | 46 -
docs/en-us/user/dependencies.md | 58 -
docs/en-us/user/languages/erlang/reference.md | 15 -
docs/en-us/user/languages/erlang/serialization.md | 17 -
docs/en-us/user/languages/erlang/service.md | 22 -
docs/en-us/user/languages/erlang/start.md | 62 -
docs/en-us/user/maturity.md | 93 -
docs/en-us/user/perf-test.md | 168 --
docs/en-us/user/preface/architecture.md | 66 -
docs/en-us/user/preface/background.md | 21 -
docs/en-us/user/preface/index.md | 1 -
docs/en-us/user/preface/requirements.md | 13 -
docs/en-us/user/preface/usage.md | 39 -
docs/en-us/user/quick-start.md | 252 --
docs/en-us/user/recommend.md | 169 --
docs/en-us/user/references/api.md | 63 -
docs/en-us/user/references/maven.md | 19 -
.../en-us/user/references/metadata/introduction.md | 369 ---
docs/en-us/user/references/protocol/dubbo.md | 110 -
docs/en-us/user/references/protocol/hessian.md | 70 -
docs/en-us/user/references/protocol/http.md | 58 -
.../en-us/user/references/protocol/introduction.md | 5 -
docs/en-us/user/references/protocol/memcached.md | 42 -
docs/en-us/user/references/protocol/redis.md | 42 -
docs/en-us/user/references/protocol/rest.md | 741 -----
docs/en-us/user/references/protocol/rmi.md | 82 -
docs/en-us/user/references/protocol/thrift.md | 32 -
docs/en-us/user/references/protocol/webservice.md | 113 -
docs/en-us/user/references/qos.md | 227 --
.../en-us/user/references/registry/introduction.md | 3 -
docs/en-us/user/references/registry/multicast.md | 38 -
docs/en-us/user/references/registry/nacos.md | 122 -
docs/en-us/user/references/registry/redis.md | 73 -
docs/en-us/user/references/registry/simple.md | 49 -
docs/en-us/user/references/registry/zookeeper.md | 154 -
docs/en-us/user/references/telnet.md | 104 -
.../en-us/user/references/xml/dubbo-application.md | 14 -
docs/en-us/user/references/xml/dubbo-argument.md | 14 -
.../user/references/xml/dubbo-config-center.md | 19 -
docs/en-us/user/references/xml/dubbo-consumer.md | 24 -
docs/en-us/user/references/xml/dubbo-method.md | 30 -
docs/en-us/user/references/xml/dubbo-module.md | 10 -
docs/en-us/user/references/xml/dubbo-monitor.md | 8 -
docs/en-us/user/references/xml/dubbo-parameter.md | 22 -
docs/en-us/user/references/xml/dubbo-protocol.md | 30 -
docs/en-us/user/references/xml/dubbo-provider.md | 50 -
docs/en-us/user/references/xml/dubbo-reference.md | 39 -
docs/en-us/user/references/xml/dubbo-registry.md | 30 -
docs/en-us/user/references/xml/dubbo-service.md | 37 -
docs/en-us/user/references/xml/introduction.md | 16 -
docs/en-us/user/rest.md | 1227 --------
docs/en-us/user/simple-monitor.md | 84 -
docs/en-us/user/sources/images/1kres.png | Bin 39384 -> 0 bytes
docs/en-us/user/sources/images/1ktps.png | Bin 38814 -> 0 bytes
docs/en-us/user/sources/images/200kres.png | Bin 39229 -> 0 bytes
docs/en-us/user/sources/images/200ktps.png | Bin 38997 -> 0 bytes
docs/en-us/user/sources/images/50kres.png | Bin 39733 -> 0 bytes
docs/en-us/user/sources/images/50ktps.png | Bin 39723 -> 0 bytes
docs/en-us/user/sources/images/arch.png | Bin 15546 -> 0 bytes
docs/en-us/user/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
docs/en-us/user/sources/images/code-coverage.jpg | Bin 141776 -> 0 bytes
docs/en-us/user/sources/images/code-dependency.jpg | Bin 138868 -> 0 bytes
docs/en-us/user/sources/images/code-quality1.jpg | Bin 56913 -> 0 bytes
docs/en-us/user/sources/images/code-quality2.jpg | Bin 56913 -> 0 bytes
docs/en-us/user/sources/images/code-quality3.jpg | Bin 56913 -> 0 bytes
docs/en-us/user/sources/images/code-quality4.jpg | Bin 56913 -> 0 bytes
docs/en-us/user/sources/images/code-quality5.jpg | Bin 41672 -> 0 bytes
docs/en-us/user/sources/images/code-quality6.jpg | Bin 41672 -> 0 bytes
docs/en-us/user/sources/images/code-quality7.jpg | Bin 41672 -> 0 bytes
docs/en-us/user/sources/images/code-tendency.jpg | Bin 54729 -> 0 bytes
docs/en-us/user/sources/images/context.png | Bin 46114 -> 0 bytes
.../sources/images/dubbo-architecture-future.jpg | Bin 55605 -> 0 bytes
.../sources/images/dubbo-architecture-roadmap.jpg | Bin 33931 -> 0 bytes
.../user/sources/images/dubbo-architecture.jpg | Bin 18810 -> 0 bytes
.../user/sources/images/dubbo-config-override.jpg | Bin 68132 -> 0 bytes
docs/en-us/user/sources/images/dubbo-config.jpg | Bin 69630 -> 0 bytes
docs/en-us/user/sources/images/dubbo-directly.jpg | Bin 38922 -> 0 bytes
.../sources/images/dubbo-properties-override.jpg | Bin 24590 -> 0 bytes
docs/en-us/user/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../user/sources/images/dubbo-redis-registry.jpg | Bin 47205 -> 0 bytes
.../sources/images/dubbo-service-governance.jpg | Bin 67000 -> 0 bytes
docs/en-us/user/sources/images/dubbo-token.jpg | Bin 17153 -> 0 bytes
docs/en-us/user/sources/images/future.jpg | Bin 20793 -> 0 bytes
docs/en-us/user/sources/images/jta-xa.jpg | Bin 37931 -> 0 bytes
docs/en-us/user/sources/images/lock-get-bean.jpg | Bin 109801 -> 0 bytes
.../user/sources/images/lock-init-context.jpg | Bin 39227 -> 0 bytes
docs/en-us/user/sources/images/multicast.jpg | Bin 20269 -> 0 bytes
docs/en-us/user/sources/images/pojores.png | Bin 37733 -> 0 bytes
docs/en-us/user/sources/images/pojotps.png | Bin 39797 -> 0 bytes
docs/en-us/user/sources/images/stub.jpg | Bin 28646 -> 0 bytes
docs/en-us/user/sources/images/subscribe-only.jpg | Bin 20626 -> 0 bytes
...pg-version=1&modificationDate=1326468174000.jpg | Bin 20626 -> 0 bytes
docs/en-us/user/sources/images/zookeeper.jpg | Bin 31272 -> 0 bytes
docs/zh-cn/admin/LICENSE | 201 --
docs/zh-cn/admin/README.md | 1 -
docs/zh-cn/admin/SUMMARY.md | 4 -
docs/zh-cn/admin/install/admin-console.md | 40 -
docs/zh-cn/admin/install/consumer-demo.md | 21 -
docs/zh-cn/admin/install/introduction.md | 13 -
docs/zh-cn/admin/install/provider-demo.md | 19 -
docs/zh-cn/admin/install/redis.md | 54 -
docs/zh-cn/admin/install/simple-monitor-center.md | 3 -
docs/zh-cn/admin/install/simple-registry-center.md | 2 -
docs/zh-cn/admin/install/zookeeper.md | 98 -
docs/zh-cn/admin/introduction.md | 65 -
docs/zh-cn/admin/ops/dubbo-ops.md | 25 -
docs/zh-cn/admin/ops/introduction.md | 1 -
docs/zh-cn/admin/ops/pinpoint.md | 415 ---
docs/zh-cn/admin/ops/skywalking.md | 133 -
docs/zh-cn/admin/serviceGovernance.md | 42 -
docs/zh-cn/admin/serviceSearch.md | 7 -
docs/zh-cn/admin/serviceTest.md | 1 -
docs/zh-cn/admin/sources/images/blackList.jpg | Bin 99079 -> 0 bytes
docs/zh-cn/admin/sources/images/config.jpg | Bin 137909 -> 0 bytes
docs/zh-cn/admin/sources/images/detail.jpg | Bin 188392 -> 0 bytes
.../admin/sources/images/dubbo-add-config.jpg | Bin 303596 -> 0 bytes
.../zh-cn/admin/sources/images/dubbo-add-route.jpg | Bin 330146 -> 0 bytes
.../admin/sources/images/dubbo-applications.png | Bin 93036 -> 0 bytes
.../zh-cn/admin/sources/images/dubbo-consumers.jpg | Bin 274307 -> 0 bytes
.../admin/sources/images/dubbo-monitor-simple.jpg | Bin 87670 -> 0 bytes
.../zh-cn/admin/sources/images/dubbo-providers.jpg | Bin 272674 -> 0 bytes
docs/zh-cn/admin/sources/images/dubbo-search.jpg | Bin 224751 -> 0 bytes
.../admin/sources/images/pinpoint-calltree.png | Bin 693731 -> 0 bytes
docs/zh-cn/admin/sources/images/pinpoint-home.png | Bin 317984 -> 0 bytes
.../admin/sources/images/pinpoint-mixedview.png | Bin 480963 -> 0 bytes
docs/zh-cn/admin/sources/images/searchResult.png | Bin 168461 -> 0 bytes
.../admin/sources/images/skywalking-alarm.png | Bin 181739 -> 0 bytes
.../sources/images/skywalking-application.png | Bin 229539 -> 0 bytes
.../images/skywalking-application_instance.png | Bin 203651 -> 0 bytes
.../admin/sources/images/skywalking-dashboard.png | Bin 257273 -> 0 bytes
.../sources/images/skywalking-service-consumer.png | Bin 282541 -> 0 bytes
.../sources/images/skywalking-service-provider.png | Bin 366038 -> 0 bytes
.../admin/sources/images/skywalking-span-Info.png | Bin 192403 -> 0 bytes
.../admin/sources/images/skywalking-topology.png | Bin 173667 -> 0 bytes
.../admin/sources/images/skywalking-trace.png | Bin 217096 -> 0 bytes
docs/zh-cn/admin/sources/images/weight.jpg | Bin 89265 -> 0 bytes
docs/zh-cn/dev/LICENSE | 201 --
docs/zh-cn/dev/README.md | 1 -
docs/zh-cn/dev/SPI.md | 237 --
docs/zh-cn/dev/SUMMARY.md | 50 -
docs/zh-cn/dev/TCK.md | 19 -
docs/zh-cn/dev/build.md | 80 -
docs/zh-cn/dev/checklist.md | 27 -
docs/zh-cn/dev/code-smell.md | 205 --
docs/zh-cn/dev/coding.md | 53 -
docs/zh-cn/dev/contract.md | 14 -
docs/zh-cn/dev/contribution.md | 45 -
docs/zh-cn/dev/design.md | 99 -
docs/zh-cn/dev/implementation.md | 226 --
docs/zh-cn/dev/impls/cache.md | 83 -
docs/zh-cn/dev/impls/cluster.md | 74 -
docs/zh-cn/dev/impls/compiler.md | 55 -
docs/zh-cn/dev/impls/config-center.md | 97 -
docs/zh-cn/dev/impls/container.md | 62 -
docs/zh-cn/dev/impls/dispatcher.md | 62 -
docs/zh-cn/dev/impls/exchanger.md | 90 -
docs/zh-cn/dev/impls/exporter-listener.md | 66 -
docs/zh-cn/dev/impls/extension-factory.md | 57 -
docs/zh-cn/dev/impls/filter.md | 89 -
docs/zh-cn/dev/impls/introduction.md | 3 -
docs/zh-cn/dev/impls/invoker-listener.md | 64 -
docs/zh-cn/dev/impls/load-balance.md | 63 -
docs/zh-cn/dev/impls/logger-adapter.md | 84 -
docs/zh-cn/dev/impls/merger.md | 60 -
docs/zh-cn/dev/impls/monitor.md | 75 -
docs/zh-cn/dev/impls/networker.md | 59 -
docs/zh-cn/dev/impls/page.md | 61 -
docs/zh-cn/dev/impls/protocol.md | 151 -
docs/zh-cn/dev/impls/proxy-factory.md | 65 -
docs/zh-cn/dev/impls/registry.md | 205 --
docs/zh-cn/dev/impls/remoting.md | 122 -
docs/zh-cn/dev/impls/router.md | 58 -
docs/zh-cn/dev/impls/serialize.md | 72 -
docs/zh-cn/dev/impls/status-checker.md | 64 -
docs/zh-cn/dev/impls/telnet-handler.md | 77 -
docs/zh-cn/dev/impls/threadpool.md | 61 -
docs/zh-cn/dev/impls/validation.md | 75 -
docs/zh-cn/dev/introduction.md | 1 -
docs/zh-cn/dev/principals/code-detail.md | 35 -
docs/zh-cn/dev/principals/configuration.md | 97 -
docs/zh-cn/dev/principals/dummy.md | 204 --
docs/zh-cn/dev/principals/expansibility.md | 18 -
docs/zh-cn/dev/principals/extension.md | 136 -
docs/zh-cn/dev/principals/general-knowledge.md | 69 -
docs/zh-cn/dev/principals/introduction.md | 3 -
docs/zh-cn/dev/principals/robustness.md | 84 -
docs/zh-cn/dev/release.md | 34 -
docs/zh-cn/dev/sources/images/close-expand.jpg | Bin 19287 -> 0 bytes
.../dev/sources/images/configuration-override.png | Bin 11422 -> 0 bytes
docs/zh-cn/dev/sources/images/ddd.jpg | Bin 19358 -> 0 bytes
docs/zh-cn/dev/sources/images/design-step1.png | Bin 121672 -> 0 bytes
docs/zh-cn/dev/sources/images/design-step2.png | Bin 141298 -> 0 bytes
docs/zh-cn/dev/sources/images/design-step3.png | Bin 165828 -> 0 bytes
docs/zh-cn/dev/sources/images/design-step4.png | Bin 240786 -> 0 bytes
docs/zh-cn/dev/sources/images/dubbo-export.jpg | Bin 70132 -> 0 bytes
docs/zh-cn/dev/sources/images/dubbo-extension.jpg | Bin 112692 -> 0 bytes
docs/zh-cn/dev/sources/images/dubbo-framework.jpg | Bin 219759 -> 0 bytes
docs/zh-cn/dev/sources/images/dubbo-modules.jpg | Bin 25411 -> 0 bytes
docs/zh-cn/dev/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
docs/zh-cn/dev/sources/images/dubbo-refer.jpg | Bin 105967 -> 0 bytes
docs/zh-cn/dev/sources/images/dubbo-relation.jpg | Bin 30304 -> 0 bytes
.../dev/sources/images/dubbo_protocol_header.png | Bin 74833 -> 0 bytes
docs/zh-cn/dev/sources/images/dubbo_rpc_export.jpg | Bin 47624 -> 0 bytes
docs/zh-cn/dev/sources/images/dubbo_rpc_invoke.jpg | Bin 45874 -> 0 bytes
docs/zh-cn/dev/sources/images/dubbo_rpc_refer.jpg | Bin 50211 -> 0 bytes
docs/zh-cn/dev/sources/images/event-listener.jpg | Bin 13192 -> 0 bytes
docs/zh-cn/dev/sources/images/filter-chain.jpg | Bin 41029 -> 0 bytes
docs/zh-cn/dev/sources/images/mix-api-spi.jpg | Bin 17004 -> 0 bytes
docs/zh-cn/dev/sources/images/open-expand.jpg | Bin 10549 -> 0 bytes
docs/zh-cn/dev/sources/images/seperate-api-spi.jpg | Bin 23683 -> 0 bytes
.../committer-guide/apache-dubbo-page_dev.md | 28 -
.../committer-guide/label-an-issue-guide_dev.md | 27 -
.../committer-guide/new-committer-guide_dev.md | 73 -
.../committer-guide/release-guide_dev.md | 477 ----
.../committer-guide/website-guide_dev.md | 5 -
.../contributor-guide/become-a-committer_dev.md | 15 -
.../contributor-guide/cla-signing-guide_dev.md | 24 -
.../contributor-guide/dubbo-extension-guide_dev.md | 47 -
.../mailing-list-subscription-guide_dev.md | 80 -
.../contributor-guide/new-contributor-guide_dev.md | 38 -
.../reporting-security-issues_dev.md | 21 -
.../software-donation-guide_dev.md | 112 -
.../contributor-guide/test-coverage-guide_dev.md | 16 -
docs/zh-cn/developers/developers_dev.md | 58 -
docs/zh-cn/developers/guide_dev.md | 82 -
docs/zh-cn/developers/user-guide/faq_dev.md | 25 -
docs/zh-cn/source_code_guide/adaptive-extension.md | 788 ------
docs/zh-cn/source_code_guide/cluster.md | 606 ----
docs/zh-cn/source_code_guide/directory.md | 542 ----
docs/zh-cn/source_code_guide/dubbo-spi.md | 432 ---
docs/zh-cn/source_code_guide/export-service.md | 1518 ----------
docs/zh-cn/source_code_guide/loadbalance.md | 767 -----
docs/zh-cn/source_code_guide/refer-service.md | 899 ------
docs/zh-cn/source_code_guide/router.md | 468 ---
.../source_code_guide/service-invoking-process.md | 1974 -------------
.../source_code_guide/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../images/consistent-hash-data-incline.jpg | Bin 101943 -> 0 bytes
.../sources/images/consistent-hash-invoker.jpg | Bin 87844 -> 0 bytes
.../sources/images/consistent-hash.jpg | Bin 95740 -> 0 bytes
.../sources/images/data-format.jpg | Bin 115165 -> 0 bytes
.../sources/images/directory-inherit-hierarchy.png | Bin 69024 -> 0 bytes
.../sources/images/dispatcher-location.jpg | Bin 89871 -> 0 bytes
.../sources/images/dubbo-spi-result.jpg | Bin 33007 -> 0 bytes
.../sources/images/java-spi-result.jpg | Bin 46805 -> 0 bytes
.../sources/images/request-id-application.jpg | Bin 217379 -> 0 bytes
.../sources/images/send-request-process.jpg | Bin 83592 -> 0 bytes
.../sources/images/send-request-thread-stack.jpg | Bin 213679 -> 0 bytes
.../sources/images/service-registry.png | Bin 57116 -> 0 bytes
docs/zh-cn/user/LICENSE | 201 --
docs/zh-cn/user/README.md | 3 -
docs/zh-cn/user/SUMMARY.md | 110 -
docs/zh-cn/user/benchmark-tool.md | 28 -
docs/zh-cn/user/best-practice.md | 69 -
docs/zh-cn/user/capacity-plan.md | 23 -
docs/zh-cn/user/configuration/annotation.md | 95 -
docs/zh-cn/user/configuration/api.md | 121 -
docs/zh-cn/user/configuration/config-center.md | 150 -
.../configuration/configuration-load-process.md | 181 --
.../user/configuration/environment-variables.md | 31 -
docs/zh-cn/user/configuration/index.md | 1 -
.../user/configuration/properties-deprecated.md | 42 -
docs/zh-cn/user/configuration/properties.md | 37 -
docs/zh-cn/user/configuration/xml.md | 91 -
docs/zh-cn/user/coveragence.md | 16 -
.../zh-cn/user/demos/GooglePb-generic-reference.md | 80 -
docs/zh-cn/user/demos/accesslog.md | 15 -
docs/zh-cn/user/demos/async-call-deprecated.md | 57 -
docs/zh-cn/user/demos/async-call.md | 134 -
docs/zh-cn/user/demos/async-execute-on-provider.md | 95 -
docs/zh-cn/user/demos/attachment.md | 30 -
docs/zh-cn/user/demos/auth.md | 28 -
docs/zh-cn/user/demos/callback-parameter.md | 112 -
docs/zh-cn/user/demos/concurrency-control.md | 68 -
docs/zh-cn/user/demos/config-connections.md | 35 -
docs/zh-cn/user/demos/config-rule-deprecated.md | 48 -
docs/zh-cn/user/demos/config-rule.md | 181 --
docs/zh-cn/user/demos/consumer-threadpool.md | 39 -
docs/zh-cn/user/demos/context.md | 40 -
docs/zh-cn/user/demos/delay-publish.md | 53 -
docs/zh-cn/user/demos/distributed-transaction.md | 9 -
docs/zh-cn/user/demos/dump.md | 18 -
docs/zh-cn/user/demos/echo-service.md | 25 -
docs/zh-cn/user/demos/events-notify.md | 97 -
docs/zh-cn/user/demos/explicit-target.md | 41 -
docs/zh-cn/user/demos/fault-tolerent-strategy.md | 78 -
docs/zh-cn/user/demos/generic-reference.md | 97 -
docs/zh-cn/user/demos/generic-service.md | 45 -
docs/zh-cn/user/demos/graceful-shutdown.md | 30 -
docs/zh-cn/user/demos/group-merger.md | 54 -
docs/zh-cn/user/demos/hostname-binding.md | 58 -
docs/zh-cn/user/demos/index.md | 1 -
docs/zh-cn/user/demos/introduction.md | 2 -
docs/zh-cn/user/demos/lazy-connect.md | 9 -
docs/zh-cn/user/demos/loadbalance.md | 60 -
docs/zh-cn/user/demos/local-call.md | 46 -
docs/zh-cn/user/demos/local-mock.md | 100 -
docs/zh-cn/user/demos/local-stub.md | 44 -
docs/zh-cn/user/demos/logger-strategy.md | 23 -
docs/zh-cn/user/demos/multi-protocols.md | 47 -
docs/zh-cn/user/demos/multi-registry.md | 84 -
docs/zh-cn/user/demos/multi-versions.md | 41 -
docs/zh-cn/user/demos/netty4.md | 35 -
docs/zh-cn/user/demos/parameter-validation.md | 183 --
docs/zh-cn/user/demos/preflight-check.md | 55 -
docs/zh-cn/user/demos/protobuf-idl.md | 31 -
docs/zh-cn/user/demos/reference-config-cache.md | 37 -
docs/zh-cn/user/demos/registry-only.md | 17 -
docs/zh-cn/user/demos/result-cache.md | 28 -
docs/zh-cn/user/demos/routing-rule-deprecated.md | 193 --
docs/zh-cn/user/demos/routing-rule.md | 250 --
docs/zh-cn/user/demos/serialization.md | 80 -
docs/zh-cn/user/demos/service-container.md | 61 -
docs/zh-cn/user/demos/service-downgrade.md | 18 -
docs/zh-cn/user/demos/service-group.md | 25 -
docs/zh-cn/user/demos/set-host.md | 59 -
docs/zh-cn/user/demos/simplify-registry-data.md | 232 --
docs/zh-cn/user/demos/static-service.md | 25 -
docs/zh-cn/user/demos/stickiness.md | 18 -
docs/zh-cn/user/demos/subscribe-only.md | 19 -
docs/zh-cn/user/demos/thread-model.md | 31 -
docs/zh-cn/user/demos/tls.md | 44 -
docs/zh-cn/user/demos/token-authorization.md | 31 -
docs/zh-cn/user/dependencies.md | 64 -
docs/zh-cn/user/languages/erlang/reference.md | 15 -
docs/zh-cn/user/languages/erlang/serialization.md | 21 -
docs/zh-cn/user/languages/erlang/service.md | 22 -
docs/zh-cn/user/languages/erlang/start.md | 60 -
docs/zh-cn/user/maturity.md | 100 -
docs/zh-cn/user/new-features-in-a-glance.md | 48 -
docs/zh-cn/user/perf-test.md | 172 --
docs/zh-cn/user/preface/architecture.md | 66 -
docs/zh-cn/user/preface/background.md | 25 -
docs/zh-cn/user/preface/index.md | 1 -
docs/zh-cn/user/preface/requirements.md | 19 -
docs/zh-cn/user/preface/usage.md | 39 -
docs/zh-cn/user/quick-start.md | 138 -
docs/zh-cn/user/recommend.md | 171 --
docs/zh-cn/user/references/api.md | 62 -
docs/zh-cn/user/references/maven.md | 19 -
.../zh-cn/user/references/metadata/introduction.md | 368 ---
.../user/references/metadata/metadata-redis.md | 1 -
.../user/references/metadata/metadata-zookeeper.md | 1 -
docs/zh-cn/user/references/protocol/dubbo.md | 123 -
docs/zh-cn/user/references/protocol/gRPC.md | 19 -
docs/zh-cn/user/references/protocol/hessian.md | 68 -
docs/zh-cn/user/references/protocol/http.md | 57 -
.../zh-cn/user/references/protocol/introduction.md | 3 -
docs/zh-cn/user/references/protocol/memcached.md | 44 -
docs/zh-cn/user/references/protocol/redis.md | 44 -
docs/zh-cn/user/references/protocol/rest.md | 741 -----
docs/zh-cn/user/references/protocol/rmi.md | 85 -
docs/zh-cn/user/references/protocol/thrift.md | 35 -
docs/zh-cn/user/references/protocol/webservice.md | 110 -
docs/zh-cn/user/references/qos.md | 241 --
.../zh-cn/user/references/registry/introduction.md | 3 -
docs/zh-cn/user/references/registry/multicast.md | 38 -
docs/zh-cn/user/references/registry/nacos.md | 130 -
docs/zh-cn/user/references/registry/redis.md | 76 -
docs/zh-cn/user/references/registry/simple.md | 49 -
docs/zh-cn/user/references/registry/zookeeper.md | 151 -
docs/zh-cn/user/references/telnet.md | 105 -
.../zh-cn/user/references/xml/dubbo-application.md | 14 -
docs/zh-cn/user/references/xml/dubbo-argument.md | 14 -
.../user/references/xml/dubbo-config-center.md | 19 -
docs/zh-cn/user/references/xml/dubbo-consumer.md | 24 -
docs/zh-cn/user/references/xml/dubbo-method.md | 30 -
docs/zh-cn/user/references/xml/dubbo-module.md | 10 -
docs/zh-cn/user/references/xml/dubbo-monitor.md | 8 -
docs/zh-cn/user/references/xml/dubbo-parameter.md | 22 -
docs/zh-cn/user/references/xml/dubbo-protocol.md | 30 -
docs/zh-cn/user/references/xml/dubbo-provider.md | 50 -
docs/zh-cn/user/references/xml/dubbo-reference.md | 33 -
docs/zh-cn/user/references/xml/dubbo-registry.md | 30 -
docs/zh-cn/user/references/xml/dubbo-service.md | 37 -
docs/zh-cn/user/references/xml/introduction.md | 15 -
docs/zh-cn/user/rest.md | 1216 --------
docs/zh-cn/user/serialization.md | 225 --
docs/zh-cn/user/simple-monitor.md | 84 -
docs/zh-cn/user/sources/images/1kres.png | Bin 39384 -> 0 bytes
docs/zh-cn/user/sources/images/1ktps.png | Bin 38814 -> 0 bytes
docs/zh-cn/user/sources/images/200kres.png | Bin 39229 -> 0 bytes
docs/zh-cn/user/sources/images/200ktps.png | Bin 38997 -> 0 bytes
docs/zh-cn/user/sources/images/50kres.png | Bin 39733 -> 0 bytes
docs/zh-cn/user/sources/images/50ktps.png | Bin 39723 -> 0 bytes
docs/zh-cn/user/sources/images/arch.png | Bin 15546 -> 0 bytes
docs/zh-cn/user/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
docs/zh-cn/user/sources/images/code-coverage.jpg | Bin 141776 -> 0 bytes
docs/zh-cn/user/sources/images/code-dependency.jpg | Bin 138868 -> 0 bytes
docs/zh-cn/user/sources/images/code-quality1.jpg | Bin 56913 -> 0 bytes
docs/zh-cn/user/sources/images/code-quality5.jpg | Bin 41672 -> 0 bytes
docs/zh-cn/user/sources/images/code-tendency.jpg | Bin 54729 -> 0 bytes
docs/zh-cn/user/sources/images/context.png | Bin 46114 -> 0 bytes
.../sources/images/dubbo-architecture-future.jpg | Bin 55605 -> 0 bytes
.../sources/images/dubbo-architecture-roadmap.jpg | Bin 33931 -> 0 bytes
.../user/sources/images/dubbo-architecture.jpg | Bin 18810 -> 0 bytes
.../user/sources/images/dubbo-config-override.jpg | Bin 68132 -> 0 bytes
docs/zh-cn/user/sources/images/dubbo-config.jpg | Bin 69630 -> 0 bytes
docs/zh-cn/user/sources/images/dubbo-directly.jpg | Bin 38922 -> 0 bytes
.../sources/images/dubbo-properties-override.jpg | Bin 24590 -> 0 bytes
docs/zh-cn/user/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../user/sources/images/dubbo-redis-registry.jpg | Bin 47205 -> 0 bytes
.../sources/images/dubbo-service-governance.jpg | Bin 67000 -> 0 bytes
docs/zh-cn/user/sources/images/dubbo-token.jpg | Bin 17153 -> 0 bytes
docs/zh-cn/user/sources/images/future.jpg | Bin 20793 -> 0 bytes
docs/zh-cn/user/sources/images/jta-xa.jpg | Bin 37931 -> 0 bytes
docs/zh-cn/user/sources/images/lock-get-bean.jpg | Bin 109801 -> 0 bytes
.../user/sources/images/lock-init-context.jpg | Bin 39227 -> 0 bytes
docs/zh-cn/user/sources/images/multicast.jpg | Bin 20269 -> 0 bytes
docs/zh-cn/user/sources/images/pojores.png | Bin 37733 -> 0 bytes
docs/zh-cn/user/sources/images/pojotps.png | Bin 39797 -> 0 bytes
docs/zh-cn/user/sources/images/rest.jpg | Bin 206610 -> 0 bytes
docs/zh-cn/user/sources/images/rt.png | Bin 31098 -> 0 bytes
docs/zh-cn/user/sources/images/stub.jpg | Bin 28646 -> 0 bytes
docs/zh-cn/user/sources/images/subscribe-only.jpg | Bin 20626 -> 0 bytes
...pg-version=1&modificationDate=1326468174000.jpg | Bin 20626 -> 0 bytes
docs/zh-cn/user/sources/images/tps.png | Bin 33114 -> 0 bytes
docs/zh-cn/user/sources/images/zookeeper.jpg | Bin 31272 -> 0 bytes
docs/zh-cn/user/versions/index.md | 3 -
docs/zh-cn/user/versions/version-270.md | 286 --
documentations/2.7/en-us/docs/admin/README.md | 3 -
documentations/2.7/en-us/docs/admin/SUMMARY.md | 4 -
.../2.7/en-us/docs/admin/install/admin-console.md | 40 -
.../2.7/en-us/docs/admin/install/consumer-demo.md | 20 -
.../2.7/en-us/docs/admin/install/introduction.md | 13 -
.../2.7/en-us/docs/admin/install/provider-demo.md | 18 -
.../2.7/en-us/docs/admin/install/redis.md | 54 -
.../docs/admin/install/simple-monitor-center.md | 3 -
.../docs/admin/install/simple-registry-center.md | 1 -
.../2.7/en-us/docs/admin/install/zookeeper.md | 98 -
.../2.7/en-us/docs/admin/introduction.md | 65 -
.../2.7/en-us/docs/admin/ops/dubbo-ops.md | 26 -
.../2.7/en-us/docs/admin/ops/introduction.md | 1 -
.../2.7/en-us/docs/admin/ops/pinpoint.md | 411 ---
.../2.7/en-us/docs/admin/ops/skywalking.md | 121 -
.../2.7/en-us/docs/admin/serviceGovernance.md | 46 -
.../2.7/en-us/docs/admin/serviceSearch.md | 7 -
documentations/2.7/en-us/docs/admin/serviceTest.md | 1 -
.../en-us/docs/admin/sources/images/blackList.jpg | Bin 99079 -> 0 bytes
.../2.7/en-us/docs/admin/sources/images/check.gif | Bin 604 -> 0 bytes
.../2.7/en-us/docs/admin/sources/images/config.jpg | Bin 137909 -> 0 bytes
.../2.7/en-us/docs/admin/sources/images/detail.jpg | Bin 188392 -> 0 bytes
.../docs/admin/sources/images/dubbo-add-config.jpg | Bin 303596 -> 0 bytes
.../docs/admin/sources/images/dubbo-add-route.jpg | Bin 330146 -> 0 bytes
.../admin/sources/images/dubbo-applications.png | Bin 93036 -> 0 bytes
.../docs/admin/sources/images/dubbo-consumers.jpg | Bin 274307 -> 0 bytes
.../admin/sources/images/dubbo-monitor-simple.jpg | Bin 87670 -> 0 bytes
.../docs/admin/sources/images/dubbo-providers.jpg | Bin 272674 -> 0 bytes
.../docs/admin/sources/images/dubbo-search.jpg | Bin 224751 -> 0 bytes
.../admin/sources/images/pinpoint-calltree.png | Bin 655223 -> 0 bytes
.../docs/admin/sources/images/pinpoint-home.png | Bin 303613 -> 0 bytes
.../admin/sources/images/pinpoint-mixedview.png | Bin 434638 -> 0 bytes
.../docs/admin/sources/images/searchResult.png | Bin 168461 -> 0 bytes
.../docs/admin/sources/images/skywalking-alarm.png | Bin 181739 -> 0 bytes
.../sources/images/skywalking-application.png | Bin 229539 -> 0 bytes
.../images/skywalking-application_instance.png | Bin 203651 -> 0 bytes
.../admin/sources/images/skywalking-dashboard.png | Bin 257273 -> 0 bytes
.../sources/images/skywalking-service-consumer.png | Bin 282541 -> 0 bytes
.../sources/images/skywalking-service-provider.png | Bin 366038 -> 0 bytes
.../admin/sources/images/skywalking-span-Info.png | Bin 192403 -> 0 bytes
.../admin/sources/images/skywalking-topology.png | Bin 173667 -> 0 bytes
.../docs/admin/sources/images/skywalking-trace.png | Bin 217096 -> 0 bytes
.../2.7/en-us/docs/admin/sources/images/tip.png | Bin 876 -> 0 bytes
.../en-us/docs/admin/sources/images/warning-3.gif | Bin 569 -> 0 bytes
.../2.7/en-us/docs/admin/sources/images/weight.jpg | Bin 89265 -> 0 bytes
documentations/2.7/en-us/docs/dev/LICENSE | 201 --
documentations/2.7/en-us/docs/dev/README.md | 3 -
documentations/2.7/en-us/docs/dev/SPI.md | 237 --
documentations/2.7/en-us/docs/dev/SUMMARY.md | 41 -
documentations/2.7/en-us/docs/dev/TCK.md | 19 -
documentations/2.7/en-us/docs/dev/build.md | 81 -
documentations/2.7/en-us/docs/dev/checklist.md | 19 -
documentations/2.7/en-us/docs/dev/code-smell.md | 205 --
documentations/2.7/en-us/docs/dev/coding.md | 53 -
documentations/2.7/en-us/docs/dev/contract.md | 14 -
documentations/2.7/en-us/docs/dev/contribution.md | 89 -
documentations/2.7/en-us/docs/dev/design.md | 99 -
.../2.7/en-us/docs/dev/implementation.md | 155 -
documentations/2.7/en-us/docs/dev/impls/cache.md | 84 -
documentations/2.7/en-us/docs/dev/impls/cluster.md | 74 -
.../2.7/en-us/docs/dev/impls/compiler.md | 55 -
.../2.7/en-us/docs/dev/impls/config-center.md | 96 -
.../2.7/en-us/docs/dev/impls/container.md | 62 -
.../2.7/en-us/docs/dev/impls/dispatcher.md | 62 -
.../2.7/en-us/docs/dev/impls/exchanger.md | 91 -
.../2.7/en-us/docs/dev/impls/exporter-listener.md | 66 -
.../2.7/en-us/docs/dev/impls/extension-factory.md | 57 -
documentations/2.7/en-us/docs/dev/impls/filter.md | 89 -
.../2.7/en-us/docs/dev/impls/introduction.md | 3 -
.../2.7/en-us/docs/dev/impls/invoker-listener.md | 65 -
.../2.7/en-us/docs/dev/impls/load-balance.md | 63 -
.../2.7/en-us/docs/dev/impls/logger-adapter.md | 84 -
documentations/2.7/en-us/docs/dev/impls/merger.md | 60 -
documentations/2.7/en-us/docs/dev/impls/monitor.md | 75 -
.../2.7/en-us/docs/dev/impls/networker.md | 59 -
documentations/2.7/en-us/docs/dev/impls/page.md | 61 -
.../2.7/en-us/docs/dev/impls/protocol.md | 150 -
.../2.7/en-us/docs/dev/impls/proxy-factory.md | 65 -
.../2.7/en-us/docs/dev/impls/registry.md | 207 --
.../2.7/en-us/docs/dev/impls/remoting.md | 122 -
documentations/2.7/en-us/docs/dev/impls/router.md | 58 -
.../2.7/en-us/docs/dev/impls/serialize.md | 72 -
.../2.7/en-us/docs/dev/impls/status-checker.md | 64 -
.../2.7/en-us/docs/dev/impls/telnet-handler.md | 77 -
.../2.7/en-us/docs/dev/impls/threadpool.md | 61 -
.../2.7/en-us/docs/dev/impls/validation.md | 75 -
documentations/2.7/en-us/docs/dev/introduction.md | 0
.../2.7/en-us/docs/dev/principals/code-detail.md | 36 -
.../2.7/en-us/docs/dev/principals/configuration.md | 83 -
.../2.7/en-us/docs/dev/principals/dummy.md | 203 --
.../2.7/en-us/docs/dev/principals/expansibility.md | 18 -
.../2.7/en-us/docs/dev/principals/extension.md | 135 -
.../en-us/docs/dev/principals/general-knowledge.md | 68 -
.../2.7/en-us/docs/dev/principals/introduction.md | 3 -
.../2.7/en-us/docs/dev/principals/robustness.md | 83 -
documentations/2.7/en-us/docs/dev/release.md | 34 -
.../en-us/docs/dev/sources/images/close-expand.jpg | Bin 19287 -> 0 bytes
.../dev/sources/images/configuration-override.png | Bin 11422 -> 0 bytes
.../2.7/en-us/docs/dev/sources/images/ddd.jpg | Bin 19358 -> 0 bytes
.../en-us/docs/dev/sources/images/design-step1.png | Bin 121672 -> 0 bytes
.../en-us/docs/dev/sources/images/design-step2.png | Bin 141298 -> 0 bytes
.../en-us/docs/dev/sources/images/design-step3.png | Bin 165828 -> 0 bytes
.../en-us/docs/dev/sources/images/design-step4.png | Bin 240786 -> 0 bytes
.../en-us/docs/dev/sources/images/dubbo-export.jpg | Bin 70132 -> 0 bytes
.../docs/dev/sources/images/dubbo-extension.jpg | Bin 112692 -> 0 bytes
.../docs/dev/sources/images/dubbo-framework.jpg | Bin 219759 -> 0 bytes
.../docs/dev/sources/images/dubbo-modules.jpg | Bin 25411 -> 0 bytes
.../docs/dev/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../en-us/docs/dev/sources/images/dubbo-refer.jpg | Bin 105967 -> 0 bytes
.../docs/dev/sources/images/dubbo-relation.jpg | Bin 30304 -> 0 bytes
.../dev/sources/images/dubbo_protocol_header.png | Bin 74833 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_export.jpg | Bin 47624 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_invoke.jpg | Bin 45874 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_refer.jpg | Bin 50211 -> 0 bytes
.../docs/dev/sources/images/event-listener.jpg | Bin 13192 -> 0 bytes
.../en-us/docs/dev/sources/images/filter-chain.jpg | Bin 41029 -> 0 bytes
.../en-us/docs/dev/sources/images/mix-api-spi.jpg | Bin 17004 -> 0 bytes
.../en-us/docs/dev/sources/images/open-expand.jpg | Bin 10549 -> 0 bytes
.../docs/dev/sources/images/seperate-api-spi.jpg | Bin 23683 -> 0 bytes
.../committer-guide/apache-dubbo-page_dev.md | 33 -
.../committer-guide/label-an-issue-guide_dev.md | 29 -
.../committer-guide/new-committer-guide_dev.md | 95 -
.../committer-guide/release-guide_dev.md | 500 ----
.../committer-guide/website-guide_dev.md | 4 -
.../contributor-guide/become-a-committer_dev.md | 15 -
.../contributor-guide/cla-signing-guide_dev.md | 25 -
.../contributor-guide/dubbo-extension-guide_dev.md | 37 -
.../mailing-list-subscription-guide_dev.md | 80 -
.../contributor-guide/new-contributor-guide_dev.md | 62 -
.../reporting-security-issues_dev.md | 21 -
.../software-donation-guide_dev.md | 106 -
.../contributor-guide/test-coverage-guide_dev.md | 16 -
.../2.7/en-us/docs/developers/developers_dev.md | 57 -
.../2.7/en-us/docs/developers/guide_dev.md | 76 -
.../en-us/docs/developers/user-guide/faq_dev.md | 27 -
documentations/2.7/en-us/docs/index.md | 4 -
documentations/2.7/en-us/docs/user/LICENSE | 201 --
documentations/2.7/en-us/docs/user/README.md | 3 -
documentations/2.7/en-us/docs/user/SUMMARY.md | 94 -
.../2.7/en-us/docs/user/benchmark-tool.md | 34 -
.../2.7/en-us/docs/user/best-practice.md | 63 -
.../2.7/en-us/docs/user/capacity-plan.md | 17 -
.../en-us/docs/user/configuration/annotation.md | 94 -
.../2.7/en-us/docs/user/configuration/api.md | 119 -
.../configuration/configuration-load-process.md | 180 --
.../2.7/en-us/docs/user/configuration/index.md | 1 -
.../en-us/docs/user/configuration/properties.md | 43 -
.../2.7/en-us/docs/user/configuration/xml.md | 77 -
documentations/2.7/en-us/docs/user/coveragence.md | 24 -
.../2.7/en-us/docs/user/demos/accesslog.md | 57 -
.../en-us/docs/user/demos/async-call-deprecated.md | 59 -
.../2.7/en-us/docs/user/demos/async-call.md | 59 -
.../docs/user/demos/async-execute-on-provider.md | 90 -
.../2.7/en-us/docs/user/demos/attachment.md | 27 -
.../en-us/docs/user/demos/callback-parameter.md | 110 -
.../en-us/docs/user/demos/concurrency-control.md | 60 -
.../en-us/docs/user/demos/config-connections.md | 30 -
.../docs/user/demos/config-rule-deprecated.md | 47 -
.../2.7/en-us/docs/user/demos/config-rule.md | 47 -
.../2.7/en-us/docs/user/demos/context.md | 39 -
.../2.7/en-us/docs/user/demos/delay-publish.md | 50 -
.../docs/user/demos/distributed-transaction.md | 7 -
documentations/2.7/en-us/docs/user/demos/dump.md | 19 -
.../2.7/en-us/docs/user/demos/echo-service.md | 25 -
.../2.7/en-us/docs/user/demos/events-notify.md | 95 -
.../2.7/en-us/docs/user/demos/explicit-target.md | 37 -
.../docs/user/demos/fault-tolerent-strategy.md | 75 -
.../2.7/en-us/docs/user/demos/generic-reference.md | 97 -
.../2.7/en-us/docs/user/demos/generic-service.md | 45 -
.../2.7/en-us/docs/user/demos/graceful-shutdown.md | 30 -
.../2.7/en-us/docs/user/demos/group-merger.md | 54 -
.../2.7/en-us/docs/user/demos/hostname-binding.md | 58 -
documentations/2.7/en-us/docs/user/demos/index.md | 1 -
.../2.7/en-us/docs/user/demos/introduction.md | 2 -
.../2.7/en-us/docs/user/demos/lazy-connect.md | 9 -
.../2.7/en-us/docs/user/demos/loadbalance.md | 64 -
.../2.7/en-us/docs/user/demos/local-call.md | 48 -
.../2.7/en-us/docs/user/demos/local-mock.md | 100 -
.../2.7/en-us/docs/user/demos/local-stub.md | 47 -
.../2.7/en-us/docs/user/demos/logger-strategy.md | 23 -
.../2.7/en-us/docs/user/demos/multi-protocols.md | 45 -
.../2.7/en-us/docs/user/demos/multi-registry.md | 83 -
.../2.7/en-us/docs/user/demos/multi-versions.md | 42 -
documentations/2.7/en-us/docs/user/demos/netty4.md | 35 -
.../en-us/docs/user/demos/parameter-validation.md | 183 --
.../2.7/en-us/docs/user/demos/preflight-check.md | 56 -
.../docs/user/demos/reference-config-cache.md | 38 -
.../2.7/en-us/docs/user/demos/registry-only.md | 19 -
.../2.7/en-us/docs/user/demos/result-cache.md | 28 -
.../2.7/en-us/docs/user/demos/routing-rule.md | 193 --
.../2.7/en-us/docs/user/demos/serialization.md | 77 -
.../2.7/en-us/docs/user/demos/service-container.md | 61 -
.../2.7/en-us/docs/user/demos/service-downgrade.md | 19 -
.../2.7/en-us/docs/user/demos/service-group.md | 27 -
.../2.7/en-us/docs/user/demos/static-service.md | 27 -
.../2.7/en-us/docs/user/demos/stickiness.md | 17 -
.../2.7/en-us/docs/user/demos/subscribe-only.md | 19 -
.../2.7/en-us/docs/user/demos/thread-model.md | 34 -
.../en-us/docs/user/demos/token-authorization.md | 46 -
documentations/2.7/en-us/docs/user/dependencies.md | 58 -
.../en-us/docs/user/languages/erlang/reference.md | 15 -
.../docs/user/languages/erlang/serialization.md | 17 -
.../en-us/docs/user/languages/erlang/service.md | 22 -
.../2.7/en-us/docs/user/languages/erlang/start.md | 62 -
documentations/2.7/en-us/docs/user/maturity.md | 93 -
documentations/2.7/en-us/docs/user/perf-test.md | 168 --
.../2.7/en-us/docs/user/preface/architecture.md | 66 -
.../2.7/en-us/docs/user/preface/background.md | 21 -
.../2.7/en-us/docs/user/preface/index.md | 1 -
.../2.7/en-us/docs/user/preface/requirements.md | 13 -
.../2.7/en-us/docs/user/preface/usage.md | 39 -
documentations/2.7/en-us/docs/user/quick-start.md | 252 --
documentations/2.7/en-us/docs/user/recommend.md | 169 --
.../2.7/en-us/docs/user/references/api.md | 63 -
.../2.7/en-us/docs/user/references/maven.md | 19 -
.../docs/user/references/metadata/introduction.md | 369 ---
.../en-us/docs/user/references/protocol/dubbo.md | 110 -
.../en-us/docs/user/references/protocol/hessian.md | 70 -
.../en-us/docs/user/references/protocol/http.md | 58 -
.../docs/user/references/protocol/introduction.md | 5 -
.../docs/user/references/protocol/memcached.md | 42 -
.../en-us/docs/user/references/protocol/redis.md | 42 -
.../en-us/docs/user/references/protocol/rest.md | 741 -----
.../2.7/en-us/docs/user/references/protocol/rmi.md | 82 -
.../en-us/docs/user/references/protocol/thrift.md | 32 -
.../docs/user/references/protocol/webservice.md | 113 -
.../2.7/en-us/docs/user/references/qos.md | 227 --
.../docs/user/references/registry/introduction.md | 3 -
.../docs/user/references/registry/multicast.md | 38 -
.../en-us/docs/user/references/registry/nacos.md | 122 -
.../en-us/docs/user/references/registry/redis.md | 73 -
.../en-us/docs/user/references/registry/simple.md | 49 -
.../docs/user/references/registry/zookeeper.md | 154 -
.../2.7/en-us/docs/user/references/telnet.md | 104 -
.../docs/user/references/xml/dubbo-application.md | 14 -
.../docs/user/references/xml/dubbo-argument.md | 14 -
.../user/references/xml/dubbo-config-center.md | 19 -
.../docs/user/references/xml/dubbo-consumer.md | 24 -
.../en-us/docs/user/references/xml/dubbo-method.md | 30 -
.../en-us/docs/user/references/xml/dubbo-module.md | 10 -
.../docs/user/references/xml/dubbo-monitor.md | 8 -
.../docs/user/references/xml/dubbo-parameter.md | 22 -
.../docs/user/references/xml/dubbo-protocol.md | 30 -
.../docs/user/references/xml/dubbo-provider.md | 50 -
.../docs/user/references/xml/dubbo-reference.md | 39 -
.../docs/user/references/xml/dubbo-registry.md | 30 -
.../docs/user/references/xml/dubbo-service.md | 37 -
.../en-us/docs/user/references/xml/introduction.md | 16 -
documentations/2.7/en-us/docs/user/rest.md | 1227 --------
.../2.7/en-us/docs/user/simple-monitor.md | 84 -
.../2.7/en-us/docs/user/sources/images/1kres.png | Bin 39384 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/1ktps.png | Bin 38814 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/200kres.png | Bin 39229 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/200ktps.png | Bin 38997 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/50kres.png | Bin 39733 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/50ktps.png | Bin 39723 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/arch.png | Bin 15546 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../docs/user/sources/images/code-coverage.jpg | Bin 141776 -> 0 bytes
.../docs/user/sources/images/code-dependency.jpg | Bin 138868 -> 0 bytes
.../docs/user/sources/images/code-quality1.jpg | Bin 56913 -> 0 bytes
.../docs/user/sources/images/code-quality2.jpg | Bin 56913 -> 0 bytes
.../docs/user/sources/images/code-quality3.jpg | Bin 56913 -> 0 bytes
.../docs/user/sources/images/code-quality4.jpg | Bin 56913 -> 0 bytes
.../docs/user/sources/images/code-quality5.jpg | Bin 41672 -> 0 bytes
.../docs/user/sources/images/code-quality6.jpg | Bin 41672 -> 0 bytes
.../docs/user/sources/images/code-quality7.jpg | Bin 41672 -> 0 bytes
.../docs/user/sources/images/code-tendency.jpg | Bin 54729 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/context.png | Bin 46114 -> 0 bytes
.../sources/images/dubbo-architecture-future.jpg | Bin 55605 -> 0 bytes
.../sources/images/dubbo-architecture-roadmap.jpg | Bin 33931 -> 0 bytes
.../user/sources/images/dubbo-architecture.jpg | Bin 18810 -> 0 bytes
.../user/sources/images/dubbo-config-override.jpg | Bin 68132 -> 0 bytes
.../docs/user/sources/images/dubbo-config.jpg | Bin 69630 -> 0 bytes
.../docs/user/sources/images/dubbo-directly.jpg | Bin 38922 -> 0 bytes
.../sources/images/dubbo-properties-override.jpg | Bin 24590 -> 0 bytes
.../docs/user/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../user/sources/images/dubbo-redis-registry.jpg | Bin 47205 -> 0 bytes
.../sources/images/dubbo-service-governance.jpg | Bin 67000 -> 0 bytes
.../en-us/docs/user/sources/images/dubbo-token.jpg | Bin 17153 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/future.jpg | Bin 20793 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/jta-xa.jpg | Bin 37931 -> 0 bytes
.../docs/user/sources/images/lock-get-bean.jpg | Bin 109801 -> 0 bytes
.../docs/user/sources/images/lock-init-context.jpg | Bin 39227 -> 0 bytes
.../en-us/docs/user/sources/images/multicast.jpg | Bin 20269 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/pojores.png | Bin 37733 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/pojotps.png | Bin 39797 -> 0 bytes
.../2.7/en-us/docs/user/sources/images/stub.jpg | Bin 28646 -> 0 bytes
.../docs/user/sources/images/subscribe-only.jpg | Bin 20626 -> 0 bytes
...pg-version=1&modificationDate=1326468174000.jpg | Bin 20626 -> 0 bytes
.../en-us/docs/user/sources/images/zookeeper.jpg | Bin 31272 -> 0 bytes
documentations/2.7/en-us/mkdocs.yml | 239 --
.../2.7/en-us/overrides/partials/tabs-item.html | 52 -
documentations/2.7/en-us/site/404.html | 701 -----
.../2.7/en-us/site/admin/SUMMARY/index.html | 716 -----
documentations/2.7/en-us/site/admin/index.html | 714 -----
.../site/admin/install/admin-console/index.html | 736 -----
.../site/admin/install/consumer-demo/index.html | 722 -----
.../site/admin/install/introduction/index.html | 715 -----
.../site/admin/install/provider-demo/index.html | 721 -----
.../2.7/en-us/site/admin/install/redis/index.html | 746 -----
.../admin/install/simple-monitor-center/index.html | 710 -----
.../install/simple-registry-center/index.html | 709 -----
.../en-us/site/admin/install/zookeeper/index.html | 778 -----
.../2.7/en-us/site/admin/introduction/index.html | 805 ------
.../2.7/en-us/site/admin/ops/dubbo-ops/index.html | 720 -----
.../en-us/site/admin/ops/introduction/index.html | 709 -----
.../2.7/en-us/site/admin/ops/pinpoint/index.html | 1092 -------
.../2.7/en-us/site/admin/ops/skywalking/index.html | 808 ------
.../en-us/site/admin/serviceGovernance/index.html | 777 -----
.../2.7/en-us/site/admin/serviceSearch/index.html | 736 -----
.../2.7/en-us/site/admin/serviceTest/index.html | 725 -----
.../en-us/site/admin/sources/images/blackList.jpg | Bin 99079 -> 0 bytes
.../2.7/en-us/site/admin/sources/images/check.gif | Bin 604 -> 0 bytes
.../2.7/en-us/site/admin/sources/images/config.jpg | Bin 137909 -> 0 bytes
.../2.7/en-us/site/admin/sources/images/detail.jpg | Bin 188392 -> 0 bytes
.../site/admin/sources/images/dubbo-add-config.jpg | Bin 303596 -> 0 bytes
.../site/admin/sources/images/dubbo-add-route.jpg | Bin 330146 -> 0 bytes
.../admin/sources/images/dubbo-applications.png | Bin 93036 -> 0 bytes
.../site/admin/sources/images/dubbo-consumers.jpg | Bin 274307 -> 0 bytes
.../admin/sources/images/dubbo-monitor-simple.jpg | Bin 87670 -> 0 bytes
.../site/admin/sources/images/dubbo-providers.jpg | Bin 272674 -> 0 bytes
.../site/admin/sources/images/dubbo-search.jpg | Bin 224751 -> 0 bytes
.../admin/sources/images/pinpoint-calltree.png | Bin 655223 -> 0 bytes
.../site/admin/sources/images/pinpoint-home.png | Bin 303613 -> 0 bytes
.../admin/sources/images/pinpoint-mixedview.png | Bin 434638 -> 0 bytes
.../site/admin/sources/images/searchResult.png | Bin 168461 -> 0 bytes
.../site/admin/sources/images/skywalking-alarm.png | Bin 181739 -> 0 bytes
.../sources/images/skywalking-application.png | Bin 229539 -> 0 bytes
.../images/skywalking-application_instance.png | Bin 203651 -> 0 bytes
.../admin/sources/images/skywalking-dashboard.png | Bin 257273 -> 0 bytes
.../sources/images/skywalking-service-consumer.png | Bin 282541 -> 0 bytes
.../sources/images/skywalking-service-provider.png | Bin 366038 -> 0 bytes
.../admin/sources/images/skywalking-span-Info.png | Bin 192403 -> 0 bytes
.../admin/sources/images/skywalking-topology.png | Bin 173667 -> 0 bytes
.../site/admin/sources/images/skywalking-trace.png | Bin 217096 -> 0 bytes
.../2.7/en-us/site/admin/sources/images/tip.png | Bin 876 -> 0 bytes
.../en-us/site/admin/sources/images/warning-3.gif | Bin 569 -> 0 bytes
.../2.7/en-us/site/admin/sources/images/weight.jpg | Bin 89265 -> 0 bytes
documentations/2.7/en-us/site/css/theme.css | 12 -
documentations/2.7/en-us/site/css/theme_extra.css | 197 --
documentations/2.7/en-us/site/dev/LICENSE | 201 --
documentations/2.7/en-us/site/dev/SPI/index.html | 916 ------
.../2.7/en-us/site/dev/SUMMARY/index.html | 751 -----
documentations/2.7/en-us/site/dev/TCK/index.html | 753 -----
documentations/2.7/en-us/site/dev/build/index.html | 796 ------
.../2.7/en-us/site/dev/checklist/index.html | 758 -----
.../2.7/en-us/site/dev/code-smell/index.html | 894 ------
.../2.7/en-us/site/dev/coding/index.html | 798 ------
.../2.7/en-us/site/dev/contract/index.html | 752 -----
.../2.7/en-us/site/dev/contribution/index.html | 1104 --------
.../2.7/en-us/site/dev/design/index.html | 837 ------
.../2.7/en-us/site/dev/implementation/index.html | 832 ------
.../2.7/en-us/site/dev/impls/cache/index.html | 816 ------
.../2.7/en-us/site/dev/impls/cluster/index.html | 809 ------
.../2.7/en-us/site/dev/impls/compiler/index.html | 790 ------
.../en-us/site/dev/impls/config-center/index.html | 785 -----
.../2.7/en-us/site/dev/impls/container/index.html | 797 ------
.../2.7/en-us/site/dev/impls/dispatcher/index.html | 797 ------
.../2.7/en-us/site/dev/impls/exchanger/index.html | 822 ------
.../site/dev/impls/exporter-listener/index.html | 798 ------
.../site/dev/impls/extension-factory/index.html | 792 ------
.../2.7/en-us/site/dev/impls/filter/index.html | 824 ------
.../en-us/site/dev/impls/introduction/index.html | 710 -----
.../site/dev/impls/invoker-listener/index.html | 798 ------
.../en-us/site/dev/impls/load-balance/index.html | 798 ------
.../en-us/site/dev/impls/logger-adapter/index.html | 815 ------
.../2.7/en-us/site/dev/impls/merger/index.html | 794 ------
.../2.7/en-us/site/dev/impls/monitor/index.html | 808 ------
.../2.7/en-us/site/dev/impls/networker/index.html | 794 ------
.../2.7/en-us/site/dev/impls/page/index.html | 796 ------
.../2.7/en-us/site/dev/impls/protocol/index.html | 882 ------
.../en-us/site/dev/impls/proxy-factory/index.html | 800 ------
.../2.7/en-us/site/dev/impls/registry/index.html | 935 ------
.../2.7/en-us/site/dev/impls/remoting/index.html | 855 ------
.../2.7/en-us/site/dev/impls/router/index.html | 793 ------
.../2.7/en-us/site/dev/impls/serialize/index.html | 809 ------
.../en-us/site/dev/impls/status-checker/index.html | 799 ------
.../en-us/site/dev/impls/telnet-handler/index.html | 812 ------
.../2.7/en-us/site/dev/impls/threadpool/index.html | 795 ------
.../2.7/en-us/site/dev/impls/validation/index.html | 806 ------
documentations/2.7/en-us/site/dev/index.html | 715 -----
.../2.7/en-us/site/dev/introduction/index.html | 709 -----
.../site/dev/principals/code-detail/index.html | 729 -----
.../site/dev/principals/configuration/index.html | 761 -----
.../2.7/en-us/site/dev/principals/dummy/index.html | 890 ------
.../site/dev/principals/expansibility/index.html | 719 -----
.../en-us/site/dev/principals/extension/index.html | 799 ------
.../dev/principals/general-knowledge/index.html | 743 -----
.../site/dev/principals/introduction/index.html | 710 -----
.../site/dev/principals/robustness/index.html | 757 -----
.../2.7/en-us/site/dev/release/index.html | 773 -----
.../en-us/site/dev/sources/images/close-expand.jpg | Bin 19287 -> 0 bytes
.../dev/sources/images/configuration-override.png | Bin 11422 -> 0 bytes
.../2.7/en-us/site/dev/sources/images/ddd.jpg | Bin 19358 -> 0 bytes
.../en-us/site/dev/sources/images/design-step1.png | Bin 121672 -> 0 bytes
.../en-us/site/dev/sources/images/design-step2.png | Bin 141298 -> 0 bytes
.../en-us/site/dev/sources/images/design-step3.png | Bin 165828 -> 0 bytes
.../en-us/site/dev/sources/images/design-step4.png | Bin 240786 -> 0 bytes
.../en-us/site/dev/sources/images/dubbo-export.jpg | Bin 70132 -> 0 bytes
.../site/dev/sources/images/dubbo-extension.jpg | Bin 112692 -> 0 bytes
.../site/dev/sources/images/dubbo-framework.jpg | Bin 219759 -> 0 bytes
.../site/dev/sources/images/dubbo-modules.jpg | Bin 25411 -> 0 bytes
.../site/dev/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../en-us/site/dev/sources/images/dubbo-refer.jpg | Bin 105967 -> 0 bytes
.../site/dev/sources/images/dubbo-relation.jpg | Bin 30304 -> 0 bytes
.../dev/sources/images/dubbo_protocol_header.png | Bin 74833 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_export.jpg | Bin 47624 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_invoke.jpg | Bin 45874 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_refer.jpg | Bin 50211 -> 0 bytes
.../site/dev/sources/images/event-listener.jpg | Bin 13192 -> 0 bytes
.../en-us/site/dev/sources/images/filter-chain.jpg | Bin 41029 -> 0 bytes
.../en-us/site/dev/sources/images/mix-api-spi.jpg | Bin 17004 -> 0 bytes
.../en-us/site/dev/sources/images/open-expand.jpg | Bin 10549 -> 0 bytes
.../site/dev/sources/images/seperate-api-spi.jpg | Bin 23683 -> 0 bytes
.../apache-dubbo-page_dev/index.html | 743 -----
.../label-an-issue-guide_dev/index.html | 741 -----
.../new-committer-guide_dev/index.html | 785 -----
.../committer-guide/release-guide_dev/index.html | 1140 --------
.../committer-guide/website-guide_dev/index.html | 713 -----
.../become-a-committer_dev/index.html | 716 -----
.../cla-signing-guide_dev/index.html | 730 -----
.../dubbo-extension-guide_dev/index.html | 742 -----
.../mailing-list-subscription-guide_dev/index.html | 789 ------
.../new-contributor-guide_dev/index.html | 756 -----
.../reporting-security-issues_dev/index.html | 722 -----
.../software-donation-guide_dev/index.html | 808 ------
.../test-coverage-guide_dev/index.html | 729 -----
.../site/developers/developers_dev/index.html | 1041 -------
.../2.7/en-us/site/developers/guide_dev/index.html | 782 -----
.../site/developers/user-guide/faq_dev/index.html | 730 -----
.../2.7/en-us/site/fonts/fontawesome-webfont.eot | Bin 37405 -> 0 bytes
.../2.7/en-us/site/fonts/fontawesome-webfont.svg | 399 ---
.../2.7/en-us/site/fonts/fontawesome-webfont.ttf | Bin 79076 -> 0 bytes
.../2.7/en-us/site/fonts/fontawesome-webfont.woff | Bin 43572 -> 0 bytes
documentations/2.7/en-us/site/img/favicon.ico | Bin 1150 -> 0 bytes
documentations/2.7/en-us/site/index.html | 727 -----
.../2.7/en-us/site/js/jquery-2.1.1.min.js | 4 -
.../2.7/en-us/site/js/modernizr-2.8.3.min.js | 1 -
documentations/2.7/en-us/site/js/theme.js | 105 -
documentations/2.7/en-us/site/search.html | 708 -----
documentations/2.7/en-us/site/search/lunr.js | 2986 --------------------
documentations/2.7/en-us/site/search/main.js | 96 -
.../2.7/en-us/site/search/search_index.json | 1 -
documentations/2.7/en-us/site/search/worker.js | 128 -
documentations/2.7/en-us/site/sitemap.xml | 648 -----
documentations/2.7/en-us/site/sitemap.xml.gz | Bin 273 -> 0 bytes
documentations/2.7/en-us/site/user/LICENSE | 201 --
.../2.7/en-us/site/user/SUMMARY/index.html | 816 ------
.../2.7/en-us/site/user/benchmark-tool/index.html | 748 -----
.../2.7/en-us/site/user/best-practice/index.html | 783 -----
.../2.7/en-us/site/user/capacity-plan/index.html | 755 -----
.../site/user/configuration/annotation/index.html | 813 ------
.../en-us/site/user/configuration/api/index.html | 852 ------
.../configuration-load-process/index.html | 866 ------
.../2.7/en-us/site/user/configuration/index.html | 714 -----
.../site/user/configuration/properties/index.html | 744 -----
.../en-us/site/user/configuration/xml/index.html | 857 ------
.../2.7/en-us/site/user/coveragence/index.html | 724 -----
.../2.7/en-us/site/user/demos/accesslog/index.html | 792 ------
.../user/demos/async-call-deprecated/index.html | 761 -----
.../en-us/site/user/demos/async-call/index.html | 783 -----
.../demos/async-execute-on-provider/index.html | 778 -----
.../en-us/site/user/demos/attachment/index.html | 762 -----
.../site/user/demos/callback-parameter/index.html | 846 ------
.../site/user/demos/concurrency-control/index.html | 796 ------
.../site/user/demos/config-connections/index.html | 732 -----
.../user/demos/config-rule-deprecated/index.html | 744 -----
.../en-us/site/user/demos/config-rule/index.html | 771 -----
.../2.7/en-us/site/user/demos/context/index.html | 774 -----
.../en-us/site/user/demos/delay-publish/index.html | 784 -----
.../user/demos/distributed-transaction/index.html | 739 -----
.../2.7/en-us/site/user/demos/dump/index.html | 751 -----
.../en-us/site/user/demos/echo-service/index.html | 753 -----
.../en-us/site/user/demos/events-notify/index.html | 832 ------
.../site/user/demos/explicit-target/index.html | 768 -----
.../user/demos/fault-tolerent-strategy/index.html | 792 ------
.../site/user/demos/generic-reference/index.html | 826 ------
.../site/user/demos/generic-service/index.html | 779 -----
.../site/user/demos/graceful-shutdown/index.html | 765 -----
.../en-us/site/user/demos/group-merger/index.html | 779 -----
.../site/user/demos/hostname-binding/index.html | 823 ------
.../2.7/en-us/site/user/demos/index.html | 714 -----
.../en-us/site/user/demos/introduction/index.html | 712 -----
.../en-us/site/user/demos/lazy-connect/index.html | 741 -----
.../en-us/site/user/demos/loadbalance/index.html | 791 ------
.../en-us/site/user/demos/local-call/index.html | 773 -----
.../en-us/site/user/demos/local-mock/index.html | 811 ------
.../en-us/site/user/demos/local-stub/index.html | 771 -----
.../site/user/demos/logger-strategy/index.html | 755 -----
.../site/user/demos/multi-protocols/index.html | 781 -----
.../site/user/demos/multi-registry/index.html | 814 ------
.../site/user/demos/multi-versions/index.html | 764 -----
.../2.7/en-us/site/user/demos/netty4/index.html | 761 -----
.../user/demos/parameter-validation/index.html | 910 ------
.../site/user/demos/preflight-check/index.html | 780 -----
.../user/demos/reference-config-cache/index.html | 734 -----
.../en-us/site/user/demos/registry-only/index.html | 748 -----
.../en-us/site/user/demos/result-cache/index.html | 763 -----
.../en-us/site/user/demos/routing-rule/index.html | 899 ------
.../en-us/site/user/demos/serialization/index.html | 804 ------
.../site/user/demos/service-container/index.html | 792 ------
.../site/user/demos/service-downgrade/index.html | 752 -----
.../en-us/site/user/demos/service-group/index.html | 760 -----
.../site/user/demos/static-service/index.html | 754 -----
.../en-us/site/user/demos/stickiness/index.html | 746 -----
.../site/user/demos/subscribe-only/index.html | 746 -----
.../en-us/site/user/demos/thread-model/index.html | 771 -----
.../site/user/demos/token-authorization/index.html | 767 -----
.../2.7/en-us/site/user/dependencies/index.html | 794 ------
documentations/2.7/en-us/site/user/index.html | 715 -----
.../user/languages/erlang/reference/index.html | 722 -----
.../user/languages/erlang/serialization/index.html | 736 -----
.../site/user/languages/erlang/service/index.html | 752 -----
.../site/user/languages/erlang/start/index.html | 757 -----
.../2.7/en-us/site/user/maturity/index.html | 1344 ---------
.../2.7/en-us/site/user/perf-test/index.html | 1080 -------
.../site/user/preface/architecture/index.html | 857 ------
.../en-us/site/user/preface/background/index.html | 758 -----
.../2.7/en-us/site/user/preface/index.html | 714 -----
.../site/user/preface/requirements/index.html | 715 -----
.../2.7/en-us/site/user/preface/usage/index.html | 773 -----
.../2.7/en-us/site/user/quick-start/index.html | 947 -------
.../2.7/en-us/site/user/recommend/index.html | 882 ------
.../2.7/en-us/site/user/references/api/index.html | 753 -----
.../en-us/site/user/references/maven/index.html | 751 -----
.../references/metadata/introduction/index.html | 1019 -------
.../site/user/references/protocol/dubbo/index.html | 850 ------
.../user/references/protocol/hessian/index.html | 798 ------
.../site/user/references/protocol/http/index.html | 791 ------
.../references/protocol/introduction/index.html | 710 -----
.../user/references/protocol/memcached/index.html | 733 -----
.../site/user/references/protocol/redis/index.html | 733 -----
.../site/user/references/protocol/rest/index.html | 1311 ---------
.../site/user/references/protocol/rmi/index.html | 811 ------
.../user/references/protocol/thrift/index.html | 768 -----
.../user/references/protocol/webservice/index.html | 793 ------
.../2.7/en-us/site/user/references/qos/index.html | 911 ------
.../references/registry/introduction/index.html | 710 -----
.../user/references/registry/multicast/index.html | 768 -----
.../site/user/references/registry/nacos/index.html | 790 ------
.../site/user/references/registry/redis/index.html | 805 ------
.../user/references/registry/simple/index.html | 780 -----
.../user/references/registry/zookeeper/index.html | 851 ------
.../en-us/site/user/references/telnet/index.html | 829 ------
.../references/xml/dubbo-application/index.html | 833 ------
.../user/references/xml/dubbo-argument/index.html | 788 ------
.../references/xml/dubbo-config-center/index.html | 869 ------
.../user/references/xml/dubbo-consumer/index.html | 933 ------
.../user/references/xml/dubbo-method/index.html | 918 ------
.../user/references/xml/dubbo-module/index.html | 793 ------
.../user/references/xml/dubbo-monitor/index.html | 773 -----
.../user/references/xml/dubbo-parameter/index.html | 782 -----
.../user/references/xml/dubbo-protocol/index.html | 993 -------
.../user/references/xml/dubbo-provider/index.html | 1193 --------
.../user/references/xml/dubbo-reference/index.html | 1023 -------
.../user/references/xml/dubbo-registry/index.html | 933 ------
.../user/references/xml/dubbo-service/index.html | 1063 -------
.../user/references/xml/introduction/index.html | 720 -----
documentations/2.7/en-us/site/user/rest/index.html | 1724 -----------
.../2.7/en-us/site/user/simple-monitor/index.html | 773 -----
.../2.7/en-us/site/user/sources/images/1kres.png | Bin 39384 -> 0 bytes
.../2.7/en-us/site/user/sources/images/1ktps.png | Bin 38814 -> 0 bytes
.../2.7/en-us/site/user/sources/images/200kres.png | Bin 39229 -> 0 bytes
.../2.7/en-us/site/user/sources/images/200ktps.png | Bin 38997 -> 0 bytes
.../2.7/en-us/site/user/sources/images/50kres.png | Bin 39733 -> 0 bytes
.../2.7/en-us/site/user/sources/images/50ktps.png | Bin 39723 -> 0 bytes
.../2.7/en-us/site/user/sources/images/arch.png | Bin 15546 -> 0 bytes
.../2.7/en-us/site/user/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../site/user/sources/images/code-coverage.jpg | Bin 141776 -> 0 bytes
.../site/user/sources/images/code-dependency.jpg | Bin 138868 -> 0 bytes
.../site/user/sources/images/code-quality1.jpg | Bin 56913 -> 0 bytes
.../site/user/sources/images/code-quality2.jpg | Bin 56913 -> 0 bytes
.../site/user/sources/images/code-quality3.jpg | Bin 56913 -> 0 bytes
.../site/user/sources/images/code-quality4.jpg | Bin 56913 -> 0 bytes
.../site/user/sources/images/code-quality5.jpg | Bin 41672 -> 0 bytes
.../site/user/sources/images/code-quality6.jpg | Bin 41672 -> 0 bytes
.../site/user/sources/images/code-quality7.jpg | Bin 41672 -> 0 bytes
.../site/user/sources/images/code-tendency.jpg | Bin 54729 -> 0 bytes
.../2.7/en-us/site/user/sources/images/context.png | Bin 46114 -> 0 bytes
.../sources/images/dubbo-architecture-future.jpg | Bin 55605 -> 0 bytes
.../sources/images/dubbo-architecture-roadmap.jpg | Bin 33931 -> 0 bytes
.../user/sources/images/dubbo-architecture.jpg | Bin 18810 -> 0 bytes
.../user/sources/images/dubbo-config-override.jpg | Bin 68132 -> 0 bytes
.../site/user/sources/images/dubbo-config.jpg | Bin 69630 -> 0 bytes
.../site/user/sources/images/dubbo-directly.jpg | Bin 38922 -> 0 bytes
.../sources/images/dubbo-properties-override.jpg | Bin 24590 -> 0 bytes
.../site/user/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../user/sources/images/dubbo-redis-registry.jpg | Bin 47205 -> 0 bytes
.../sources/images/dubbo-service-governance.jpg | Bin 67000 -> 0 bytes
.../en-us/site/user/sources/images/dubbo-token.jpg | Bin 17153 -> 0 bytes
.../2.7/en-us/site/user/sources/images/future.jpg | Bin 20793 -> 0 bytes
.../2.7/en-us/site/user/sources/images/jta-xa.jpg | Bin 37931 -> 0 bytes
.../site/user/sources/images/lock-get-bean.jpg | Bin 109801 -> 0 bytes
.../site/user/sources/images/lock-init-context.jpg | Bin 39227 -> 0 bytes
.../en-us/site/user/sources/images/multicast.jpg | Bin 20269 -> 0 bytes
.../2.7/en-us/site/user/sources/images/pojores.png | Bin 37733 -> 0 bytes
.../2.7/en-us/site/user/sources/images/pojotps.png | Bin 39797 -> 0 bytes
.../2.7/en-us/site/user/sources/images/stub.jpg | Bin 28646 -> 0 bytes
.../site/user/sources/images/subscribe-only.jpg | Bin 20626 -> 0 bytes
...pg-version=1&modificationDate=1326468174000.jpg | Bin 20626 -> 0 bytes
.../en-us/site/user/sources/images/zookeeper.jpg | Bin 31272 -> 0 bytes
documentations/2.7/zh-cn/docs/admin/LICENSE | 201 --
documentations/2.7/zh-cn/docs/admin/README.md | 1 -
documentations/2.7/zh-cn/docs/admin/SUMMARY.md | 4 -
.../2.7/zh-cn/docs/admin/install/admin-console.md | 40 -
.../2.7/zh-cn/docs/admin/install/consumer-demo.md | 21 -
.../2.7/zh-cn/docs/admin/install/introduction.md | 13 -
.../2.7/zh-cn/docs/admin/install/provider-demo.md | 19 -
.../2.7/zh-cn/docs/admin/install/redis.md | 54 -
.../docs/admin/install/simple-monitor-center.md | 3 -
.../docs/admin/install/simple-registry-center.md | 2 -
.../2.7/zh-cn/docs/admin/install/zookeeper.md | 98 -
.../2.7/zh-cn/docs/admin/introduction.md | 65 -
.../2.7/zh-cn/docs/admin/ops/dubbo-ops.md | 25 -
.../2.7/zh-cn/docs/admin/ops/introduction.md | 1 -
.../2.7/zh-cn/docs/admin/ops/pinpoint.md | 415 ---
.../2.7/zh-cn/docs/admin/ops/skywalking.md | 133 -
.../2.7/zh-cn/docs/admin/serviceGovernance.md | 42 -
.../2.7/zh-cn/docs/admin/serviceSearch.md | 7 -
documentations/2.7/zh-cn/docs/admin/serviceTest.md | 1 -
.../zh-cn/docs/admin/sources/images/blackList.jpg | Bin 99079 -> 0 bytes
.../2.7/zh-cn/docs/admin/sources/images/config.jpg | Bin 137909 -> 0 bytes
.../2.7/zh-cn/docs/admin/sources/images/detail.jpg | Bin 188392 -> 0 bytes
.../docs/admin/sources/images/dubbo-add-config.jpg | Bin 303596 -> 0 bytes
.../docs/admin/sources/images/dubbo-add-route.jpg | Bin 330146 -> 0 bytes
.../admin/sources/images/dubbo-applications.png | Bin 93036 -> 0 bytes
.../docs/admin/sources/images/dubbo-consumers.jpg | Bin 274307 -> 0 bytes
.../admin/sources/images/dubbo-monitor-simple.jpg | Bin 87670 -> 0 bytes
.../docs/admin/sources/images/dubbo-providers.jpg | Bin 272674 -> 0 bytes
.../docs/admin/sources/images/dubbo-search.jpg | Bin 224751 -> 0 bytes
.../admin/sources/images/pinpoint-calltree.png | Bin 693731 -> 0 bytes
.../docs/admin/sources/images/pinpoint-home.png | Bin 317984 -> 0 bytes
.../admin/sources/images/pinpoint-mixedview.png | Bin 480963 -> 0 bytes
.../docs/admin/sources/images/searchResult.png | Bin 168461 -> 0 bytes
.../docs/admin/sources/images/skywalking-alarm.png | Bin 181739 -> 0 bytes
.../sources/images/skywalking-application.png | Bin 229539 -> 0 bytes
.../images/skywalking-application_instance.png | Bin 203651 -> 0 bytes
.../admin/sources/images/skywalking-dashboard.png | Bin 257273 -> 0 bytes
.../sources/images/skywalking-service-consumer.png | Bin 282541 -> 0 bytes
.../sources/images/skywalking-service-provider.png | Bin 366038 -> 0 bytes
.../admin/sources/images/skywalking-span-Info.png | Bin 192403 -> 0 bytes
.../admin/sources/images/skywalking-topology.png | Bin 173667 -> 0 bytes
.../docs/admin/sources/images/skywalking-trace.png | Bin 217096 -> 0 bytes
.../2.7/zh-cn/docs/admin/sources/images/weight.jpg | Bin 89265 -> 0 bytes
documentations/2.7/zh-cn/docs/dev/LICENSE | 201 --
documentations/2.7/zh-cn/docs/dev/README.md | 1 -
documentations/2.7/zh-cn/docs/dev/SPI.md | 237 --
documentations/2.7/zh-cn/docs/dev/SUMMARY.md | 50 -
documentations/2.7/zh-cn/docs/dev/TCK.md | 19 -
documentations/2.7/zh-cn/docs/dev/build.md | 80 -
documentations/2.7/zh-cn/docs/dev/checklist.md | 27 -
documentations/2.7/zh-cn/docs/dev/code-smell.md | 205 --
documentations/2.7/zh-cn/docs/dev/coding.md | 53 -
documentations/2.7/zh-cn/docs/dev/contract.md | 14 -
documentations/2.7/zh-cn/docs/dev/contribution.md | 45 -
documentations/2.7/zh-cn/docs/dev/design.md | 99 -
.../2.7/zh-cn/docs/dev/implementation.md | 226 --
documentations/2.7/zh-cn/docs/dev/impls/cache.md | 83 -
documentations/2.7/zh-cn/docs/dev/impls/cluster.md | 74 -
.../2.7/zh-cn/docs/dev/impls/compiler.md | 55 -
.../2.7/zh-cn/docs/dev/impls/config-center.md | 97 -
.../2.7/zh-cn/docs/dev/impls/container.md | 62 -
.../2.7/zh-cn/docs/dev/impls/dispatcher.md | 62 -
.../2.7/zh-cn/docs/dev/impls/exchanger.md | 90 -
.../2.7/zh-cn/docs/dev/impls/exporter-listener.md | 66 -
.../2.7/zh-cn/docs/dev/impls/extension-factory.md | 57 -
documentations/2.7/zh-cn/docs/dev/impls/filter.md | 89 -
.../2.7/zh-cn/docs/dev/impls/introduction.md | 3 -
.../2.7/zh-cn/docs/dev/impls/invoker-listener.md | 64 -
.../2.7/zh-cn/docs/dev/impls/load-balance.md | 63 -
.../2.7/zh-cn/docs/dev/impls/logger-adapter.md | 84 -
documentations/2.7/zh-cn/docs/dev/impls/merger.md | 60 -
documentations/2.7/zh-cn/docs/dev/impls/monitor.md | 75 -
.../2.7/zh-cn/docs/dev/impls/networker.md | 59 -
documentations/2.7/zh-cn/docs/dev/impls/page.md | 61 -
.../2.7/zh-cn/docs/dev/impls/protocol.md | 151 -
.../2.7/zh-cn/docs/dev/impls/proxy-factory.md | 65 -
.../2.7/zh-cn/docs/dev/impls/registry.md | 205 --
.../2.7/zh-cn/docs/dev/impls/remoting.md | 122 -
documentations/2.7/zh-cn/docs/dev/impls/router.md | 58 -
.../2.7/zh-cn/docs/dev/impls/serialize.md | 72 -
.../2.7/zh-cn/docs/dev/impls/status-checker.md | 64 -
.../2.7/zh-cn/docs/dev/impls/telnet-handler.md | 77 -
.../2.7/zh-cn/docs/dev/impls/threadpool.md | 61 -
.../2.7/zh-cn/docs/dev/impls/validation.md | 75 -
documentations/2.7/zh-cn/docs/dev/introduction.md | 1 -
.../2.7/zh-cn/docs/dev/principals/code-detail.md | 35 -
.../2.7/zh-cn/docs/dev/principals/configuration.md | 97 -
.../2.7/zh-cn/docs/dev/principals/dummy.md | 204 --
.../2.7/zh-cn/docs/dev/principals/expansibility.md | 18 -
.../2.7/zh-cn/docs/dev/principals/extension.md | 136 -
.../zh-cn/docs/dev/principals/general-knowledge.md | 69 -
.../2.7/zh-cn/docs/dev/principals/introduction.md | 3 -
.../2.7/zh-cn/docs/dev/principals/robustness.md | 84 -
documentations/2.7/zh-cn/docs/dev/release.md | 34 -
.../zh-cn/docs/dev/sources/images/close-expand.jpg | Bin 19287 -> 0 bytes
.../dev/sources/images/configuration-override.png | Bin 11422 -> 0 bytes
.../2.7/zh-cn/docs/dev/sources/images/ddd.jpg | Bin 19358 -> 0 bytes
.../zh-cn/docs/dev/sources/images/design-step1.png | Bin 121672 -> 0 bytes
.../zh-cn/docs/dev/sources/images/design-step2.png | Bin 141298 -> 0 bytes
.../zh-cn/docs/dev/sources/images/design-step3.png | Bin 165828 -> 0 bytes
.../zh-cn/docs/dev/sources/images/design-step4.png | Bin 240786 -> 0 bytes
.../zh-cn/docs/dev/sources/images/dubbo-export.jpg | Bin 70132 -> 0 bytes
.../docs/dev/sources/images/dubbo-extension.jpg | Bin 112692 -> 0 bytes
.../docs/dev/sources/images/dubbo-framework.jpg | Bin 219759 -> 0 bytes
.../docs/dev/sources/images/dubbo-modules.jpg | Bin 25411 -> 0 bytes
.../docs/dev/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../zh-cn/docs/dev/sources/images/dubbo-refer.jpg | Bin 105967 -> 0 bytes
.../docs/dev/sources/images/dubbo-relation.jpg | Bin 30304 -> 0 bytes
.../dev/sources/images/dubbo_protocol_header.png | Bin 74833 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_export.jpg | Bin 47624 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_invoke.jpg | Bin 45874 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_refer.jpg | Bin 50211 -> 0 bytes
.../docs/dev/sources/images/event-listener.jpg | Bin 13192 -> 0 bytes
.../zh-cn/docs/dev/sources/images/filter-chain.jpg | Bin 41029 -> 0 bytes
.../zh-cn/docs/dev/sources/images/mix-api-spi.jpg | Bin 17004 -> 0 bytes
.../zh-cn/docs/dev/sources/images/open-expand.jpg | Bin 10549 -> 0 bytes
.../docs/dev/sources/images/seperate-api-spi.jpg | Bin 23683 -> 0 bytes
.../committer-guide/apache-dubbo-page_dev.md | 28 -
.../committer-guide/label-an-issue-guide_dev.md | 27 -
.../committer-guide/new-committer-guide_dev.md | 73 -
.../committer-guide/release-guide_dev.md | 477 ----
.../committer-guide/website-guide_dev.md | 5 -
.../contributor-guide/become-a-committer_dev.md | 15 -
.../contributor-guide/cla-signing-guide_dev.md | 24 -
.../contributor-guide/dubbo-extension-guide_dev.md | 47 -
.../mailing-list-subscription-guide_dev.md | 80 -
.../contributor-guide/new-contributor-guide_dev.md | 38 -
.../reporting-security-issues_dev.md | 21 -
.../software-donation-guide_dev.md | 112 -
.../contributor-guide/test-coverage-guide_dev.md | 16 -
.../2.7/zh-cn/docs/developers/developers_dev.md | 58 -
.../2.7/zh-cn/docs/developers/guide_dev.md | 82 -
.../zh-cn/docs/developers/user-guide/faq_dev.md | 25 -
documentations/2.7/zh-cn/docs/index.md | 15 -
.../docs/source_code_guide/adaptive-extension.md | 788 ------
.../2.7/zh-cn/docs/source_code_guide/cluster.md | 606 ----
.../2.7/zh-cn/docs/source_code_guide/directory.md | 542 ----
.../2.7/zh-cn/docs/source_code_guide/dubbo-spi.md | 432 ---
.../zh-cn/docs/source_code_guide/export-service.md | 1518 ----------
.../zh-cn/docs/source_code_guide/loadbalance.md | 767 -----
.../zh-cn/docs/source_code_guide/refer-service.md | 899 ------
.../2.7/zh-cn/docs/source_code_guide/router.md | 468 ---
.../source_code_guide/service-invoking-process.md | 1974 -------------
.../source_code_guide/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../images/consistent-hash-data-incline.jpg | Bin 101943 -> 0 bytes
.../sources/images/consistent-hash-invoker.jpg | Bin 87844 -> 0 bytes
.../sources/images/consistent-hash.jpg | Bin 95740 -> 0 bytes
.../sources/images/data-format.jpg | Bin 115165 -> 0 bytes
.../sources/images/directory-inherit-hierarchy.png | Bin 69024 -> 0 bytes
.../sources/images/dispatcher-location.jpg | Bin 89871 -> 0 bytes
.../sources/images/dubbo-spi-result.jpg | Bin 33007 -> 0 bytes
.../sources/images/java-spi-result.jpg | Bin 46805 -> 0 bytes
.../sources/images/request-id-application.jpg | Bin 217379 -> 0 bytes
.../sources/images/send-request-process.jpg | Bin 83592 -> 0 bytes
.../sources/images/send-request-thread-stack.jpg | Bin 213679 -> 0 bytes
.../sources/images/service-registry.png | Bin 57116 -> 0 bytes
documentations/2.7/zh-cn/docs/user/LICENSE | 201 --
documentations/2.7/zh-cn/docs/user/README.md | 3 -
documentations/2.7/zh-cn/docs/user/SUMMARY.md | 110 -
.../2.7/zh-cn/docs/user/benchmark-tool.md | 28 -
.../2.7/zh-cn/docs/user/best-practice.md | 69 -
.../2.7/zh-cn/docs/user/capacity-plan.md | 23 -
.../zh-cn/docs/user/configuration/annotation.md | 95 -
.../2.7/zh-cn/docs/user/configuration/api.md | 121 -
.../zh-cn/docs/user/configuration/config-center.md | 150 -
.../configuration/configuration-load-process.md | 181 --
.../user/configuration/environment-variables.md | 31 -
.../2.7/zh-cn/docs/user/configuration/index.md | 1 -
.../user/configuration/properties-deprecated.md | 42 -
.../zh-cn/docs/user/configuration/properties.md | 37 -
.../2.7/zh-cn/docs/user/configuration/xml.md | 91 -
documentations/2.7/zh-cn/docs/user/coveragence.md | 16 -
.../docs/user/demos/GooglePb-generic-reference.md | 80 -
.../2.7/zh-cn/docs/user/demos/accesslog.md | 15 -
.../zh-cn/docs/user/demos/async-call-deprecated.md | 57 -
.../2.7/zh-cn/docs/user/demos/async-call.md | 134 -
.../docs/user/demos/async-execute-on-provider.md | 95 -
.../2.7/zh-cn/docs/user/demos/attachment.md | 30 -
documentations/2.7/zh-cn/docs/user/demos/auth.md | 28 -
.../zh-cn/docs/user/demos/callback-parameter.md | 112 -
.../zh-cn/docs/user/demos/concurrency-control.md | 68 -
.../zh-cn/docs/user/demos/config-connections.md | 35 -
.../docs/user/demos/config-rule-deprecated.md | 48 -
.../2.7/zh-cn/docs/user/demos/config-rule.md | 181 --
.../zh-cn/docs/user/demos/consumer-threadpool.md | 41 -
.../2.7/zh-cn/docs/user/demos/context.md | 40 -
.../2.7/zh-cn/docs/user/demos/delay-publish.md | 53 -
.../docs/user/demos/distributed-transaction.md | 9 -
documentations/2.7/zh-cn/docs/user/demos/dump.md | 18 -
.../2.7/zh-cn/docs/user/demos/echo-service.md | 25 -
.../2.7/zh-cn/docs/user/demos/events-notify.md | 97 -
.../2.7/zh-cn/docs/user/demos/explicit-target.md | 41 -
.../docs/user/demos/fault-tolerent-strategy.md | 78 -
.../2.7/zh-cn/docs/user/demos/generic-reference.md | 97 -
.../2.7/zh-cn/docs/user/demos/generic-service.md | 45 -
.../2.7/zh-cn/docs/user/demos/graceful-shutdown.md | 30 -
.../2.7/zh-cn/docs/user/demos/group-merger.md | 54 -
.../2.7/zh-cn/docs/user/demos/hostname-binding.md | 58 -
documentations/2.7/zh-cn/docs/user/demos/index.md | 1 -
.../2.7/zh-cn/docs/user/demos/introduction.md | 2 -
.../2.7/zh-cn/docs/user/demos/lazy-connect.md | 9 -
.../2.7/zh-cn/docs/user/demos/loadbalance.md | 60 -
.../2.7/zh-cn/docs/user/demos/local-call.md | 46 -
.../2.7/zh-cn/docs/user/demos/local-mock.md | 100 -
.../2.7/zh-cn/docs/user/demos/local-stub.md | 44 -
.../2.7/zh-cn/docs/user/demos/logger-strategy.md | 23 -
.../2.7/zh-cn/docs/user/demos/multi-protocols.md | 47 -
.../2.7/zh-cn/docs/user/demos/multi-registry.md | 84 -
.../2.7/zh-cn/docs/user/demos/multi-versions.md | 41 -
documentations/2.7/zh-cn/docs/user/demos/netty4.md | 35 -
.../zh-cn/docs/user/demos/parameter-validation.md | 183 --
.../2.7/zh-cn/docs/user/demos/preflight-check.md | 55 -
.../2.7/zh-cn/docs/user/demos/protobuf-idl.md | 31 -
.../docs/user/demos/reference-config-cache.md | 37 -
.../2.7/zh-cn/docs/user/demos/registry-only.md | 17 -
.../2.7/zh-cn/docs/user/demos/result-cache.md | 28 -
.../docs/user/demos/routing-rule-deprecated.md | 193 --
.../2.7/zh-cn/docs/user/demos/routing-rule.md | 250 --
.../2.7/zh-cn/docs/user/demos/serialization.md | 80 -
.../2.7/zh-cn/docs/user/demos/service-container.md | 61 -
.../2.7/zh-cn/docs/user/demos/service-downgrade.md | 18 -
.../2.7/zh-cn/docs/user/demos/service-group.md | 25 -
.../2.7/zh-cn/docs/user/demos/set-host.md | 59 -
.../docs/user/demos/simplify-registry-data.md | 232 --
.../2.7/zh-cn/docs/user/demos/static-service.md | 25 -
.../2.7/zh-cn/docs/user/demos/stickiness.md | 18 -
.../2.7/zh-cn/docs/user/demos/subscribe-only.md | 19 -
.../2.7/zh-cn/docs/user/demos/thread-model.md | 31 -
documentations/2.7/zh-cn/docs/user/demos/tls.md | 44 -
.../zh-cn/docs/user/demos/token-authorization.md | 31 -
documentations/2.7/zh-cn/docs/user/dependencies.md | 64 -
.../zh-cn/docs/user/languages/erlang/reference.md | 15 -
.../docs/user/languages/erlang/serialization.md | 21 -
.../zh-cn/docs/user/languages/erlang/service.md | 22 -
.../2.7/zh-cn/docs/user/languages/erlang/start.md | 60 -
documentations/2.7/zh-cn/docs/user/maturity.md | 100 -
.../zh-cn/docs/user/new-features-in-a-glance.md | 48 -
documentations/2.7/zh-cn/docs/user/perf-test.md | 172 --
.../2.7/zh-cn/docs/user/preface/architecture.md | 66 -
.../2.7/zh-cn/docs/user/preface/background.md | 25 -
.../2.7/zh-cn/docs/user/preface/index.md | 1 -
.../2.7/zh-cn/docs/user/preface/requirements.md | 19 -
.../2.7/zh-cn/docs/user/preface/usage.md | 39 -
documentations/2.7/zh-cn/docs/user/quick-start.md | 138 -
documentations/2.7/zh-cn/docs/user/recommend.md | 171 --
.../2.7/zh-cn/docs/user/references/api.md | 62 -
.../2.7/zh-cn/docs/user/references/maven.md | 19 -
.../docs/user/references/metadata/introduction.md | 368 ---
.../user/references/metadata/metadata-redis.md | 1 -
.../user/references/metadata/metadata-zookeeper.md | 1 -
.../zh-cn/docs/user/references/protocol/dubbo.md | 123 -
.../zh-cn/docs/user/references/protocol/gRPC.md | 19 -
.../zh-cn/docs/user/references/protocol/hessian.md | 68 -
.../zh-cn/docs/user/references/protocol/http.md | 57 -
.../docs/user/references/protocol/introduction.md | 3 -
.../docs/user/references/protocol/memcached.md | 44 -
.../zh-cn/docs/user/references/protocol/redis.md | 44 -
.../zh-cn/docs/user/references/protocol/rest.md | 741 -----
.../2.7/zh-cn/docs/user/references/protocol/rmi.md | 85 -
.../zh-cn/docs/user/references/protocol/thrift.md | 35 -
.../docs/user/references/protocol/webservice.md | 110 -
.../2.7/zh-cn/docs/user/references/qos.md | 241 --
.../docs/user/references/registry/introduction.md | 3 -
.../docs/user/references/registry/multicast.md | 38 -
.../zh-cn/docs/user/references/registry/nacos.md | 130 -
.../zh-cn/docs/user/references/registry/redis.md | 76 -
.../zh-cn/docs/user/references/registry/simple.md | 49 -
.../docs/user/references/registry/zookeeper.md | 151 -
.../2.7/zh-cn/docs/user/references/telnet.md | 105 -
.../docs/user/references/xml/dubbo-application.md | 14 -
.../docs/user/references/xml/dubbo-argument.md | 14 -
.../user/references/xml/dubbo-config-center.md | 19 -
.../docs/user/references/xml/dubbo-consumer.md | 24 -
.../zh-cn/docs/user/references/xml/dubbo-method.md | 30 -
.../zh-cn/docs/user/references/xml/dubbo-module.md | 10 -
.../docs/user/references/xml/dubbo-monitor.md | 8 -
.../docs/user/references/xml/dubbo-parameter.md | 22 -
.../docs/user/references/xml/dubbo-protocol.md | 30 -
.../docs/user/references/xml/dubbo-provider.md | 50 -
.../docs/user/references/xml/dubbo-reference.md | 33 -
.../docs/user/references/xml/dubbo-registry.md | 30 -
.../docs/user/references/xml/dubbo-service.md | 37 -
.../zh-cn/docs/user/references/xml/introduction.md | 15 -
documentations/2.7/zh-cn/docs/user/rest.md | 1216 --------
.../2.7/zh-cn/docs/user/serialization.md | 225 --
.../2.7/zh-cn/docs/user/simple-monitor.md | 84 -
.../2.7/zh-cn/docs/user/sources/images/1kres.png | Bin 39384 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/1ktps.png | Bin 38814 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/200kres.png | Bin 39229 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/200ktps.png | Bin 38997 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/50kres.png | Bin 39733 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/50ktps.png | Bin 39723 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/arch.png | Bin 15546 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../docs/user/sources/images/code-coverage.jpg | Bin 141776 -> 0 bytes
.../docs/user/sources/images/code-dependency.jpg | Bin 138868 -> 0 bytes
.../docs/user/sources/images/code-quality1.jpg | Bin 56913 -> 0 bytes
.../docs/user/sources/images/code-quality5.jpg | Bin 41672 -> 0 bytes
.../docs/user/sources/images/code-tendency.jpg | Bin 54729 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/context.png | Bin 46114 -> 0 bytes
.../sources/images/dubbo-architecture-future.jpg | Bin 55605 -> 0 bytes
.../sources/images/dubbo-architecture-roadmap.jpg | Bin 33931 -> 0 bytes
.../user/sources/images/dubbo-architecture.jpg | Bin 18810 -> 0 bytes
.../user/sources/images/dubbo-config-override.jpg | Bin 68132 -> 0 bytes
.../docs/user/sources/images/dubbo-config.jpg | Bin 69630 -> 0 bytes
.../docs/user/sources/images/dubbo-directly.jpg | Bin 38922 -> 0 bytes
.../sources/images/dubbo-properties-override.jpg | Bin 24590 -> 0 bytes
.../docs/user/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../user/sources/images/dubbo-redis-registry.jpg | Bin 47205 -> 0 bytes
.../sources/images/dubbo-service-governance.jpg | Bin 67000 -> 0 bytes
.../zh-cn/docs/user/sources/images/dubbo-token.jpg | Bin 17153 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/future.jpg | Bin 20793 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/jta-xa.jpg | Bin 37931 -> 0 bytes
.../docs/user/sources/images/lock-get-bean.jpg | Bin 109801 -> 0 bytes
.../docs/user/sources/images/lock-init-context.jpg | Bin 39227 -> 0 bytes
.../zh-cn/docs/user/sources/images/multicast.jpg | Bin 20269 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/pojores.png | Bin 37733 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/pojotps.png | Bin 39797 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/rest.jpg | Bin 206610 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/rt.png | Bin 31098 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/stub.jpg | Bin 28646 -> 0 bytes
.../docs/user/sources/images/subscribe-only.jpg | Bin 20626 -> 0 bytes
...pg-version=1&modificationDate=1326468174000.jpg | Bin 20626 -> 0 bytes
.../2.7/zh-cn/docs/user/sources/images/tps.png | Bin 33114 -> 0 bytes
.../zh-cn/docs/user/sources/images/zookeeper.jpg | Bin 31272 -> 0 bytes
.../2.7/zh-cn/docs/user/versions/index.md | 3 -
.../2.7/zh-cn/docs/user/versions/version-270.md | 286 --
documentations/2.7/zh-cn/mkdocs.yml | 172 --
documentations/2.7/zh-cn/site/404.html | 769 -----
documentations/2.7/zh-cn/site/admin/LICENSE | 201 --
.../2.7/zh-cn/site/admin/SUMMARY/index.html | 784 -----
documentations/2.7/zh-cn/site/admin/index.html | 782 -----
.../site/admin/install/admin-console/index.html | 802 ------
.../site/admin/install/consumer-demo/index.html | 790 ------
.../site/admin/install/introduction/index.html | 783 -----
.../site/admin/install/provider-demo/index.html | 789 ------
.../2.7/zh-cn/site/admin/install/redis/index.html | 814 ------
.../admin/install/simple-monitor-center/index.html | 778 -----
.../install/simple-registry-center/index.html | 777 -----
.../zh-cn/site/admin/install/zookeeper/index.html | 846 ------
.../2.7/zh-cn/site/admin/introduction/index.html | 871 ------
.../2.7/zh-cn/site/admin/ops/dubbo-ops/index.html | 789 ------
.../zh-cn/site/admin/ops/introduction/index.html | 777 -----
.../2.7/zh-cn/site/admin/ops/pinpoint/index.html | 1168 --------
.../2.7/zh-cn/site/admin/ops/skywalking/index.html | 888 ------
.../zh-cn/site/admin/serviceGovernance/index.html | 841 ------
.../2.7/zh-cn/site/admin/serviceSearch/index.html | 804 ------
.../2.7/zh-cn/site/admin/serviceTest/index.html | 793 ------
.../zh-cn/site/admin/sources/images/blackList.jpg | Bin 99079 -> 0 bytes
.../2.7/zh-cn/site/admin/sources/images/config.jpg | Bin 137909 -> 0 bytes
.../2.7/zh-cn/site/admin/sources/images/detail.jpg | Bin 188392 -> 0 bytes
.../site/admin/sources/images/dubbo-add-config.jpg | Bin 303596 -> 0 bytes
.../site/admin/sources/images/dubbo-add-route.jpg | Bin 330146 -> 0 bytes
.../admin/sources/images/dubbo-applications.png | Bin 93036 -> 0 bytes
.../site/admin/sources/images/dubbo-consumers.jpg | Bin 274307 -> 0 bytes
.../admin/sources/images/dubbo-monitor-simple.jpg | Bin 87670 -> 0 bytes
.../site/admin/sources/images/dubbo-providers.jpg | Bin 272674 -> 0 bytes
.../site/admin/sources/images/dubbo-search.jpg | Bin 224751 -> 0 bytes
.../admin/sources/images/pinpoint-calltree.png | Bin 693731 -> 0 bytes
.../site/admin/sources/images/pinpoint-home.png | Bin 317984 -> 0 bytes
.../admin/sources/images/pinpoint-mixedview.png | Bin 480963 -> 0 bytes
.../site/admin/sources/images/searchResult.png | Bin 168461 -> 0 bytes
.../site/admin/sources/images/skywalking-alarm.png | Bin 181739 -> 0 bytes
.../sources/images/skywalking-application.png | Bin 229539 -> 0 bytes
.../images/skywalking-application_instance.png | Bin 203651 -> 0 bytes
.../admin/sources/images/skywalking-dashboard.png | Bin 257273 -> 0 bytes
.../sources/images/skywalking-service-consumer.png | Bin 282541 -> 0 bytes
.../sources/images/skywalking-service-provider.png | Bin 366038 -> 0 bytes
.../admin/sources/images/skywalking-span-Info.png | Bin 192403 -> 0 bytes
.../admin/sources/images/skywalking-topology.png | Bin 173667 -> 0 bytes
.../site/admin/sources/images/skywalking-trace.png | Bin 217096 -> 0 bytes
.../2.7/zh-cn/site/admin/sources/images/weight.jpg | Bin 89265 -> 0 bytes
documentations/2.7/zh-cn/site/css/theme.css | 12 -
documentations/2.7/zh-cn/site/css/theme_extra.css | 197 --
documentations/2.7/zh-cn/site/dev/LICENSE | 201 --
documentations/2.7/zh-cn/site/dev/SPI/index.html | 984 -------
.../2.7/zh-cn/site/dev/SUMMARY/index.html | 830 ------
documentations/2.7/zh-cn/site/dev/TCK/index.html | 821 ------
documentations/2.7/zh-cn/site/dev/build/index.html | 864 ------
.../2.7/zh-cn/site/dev/checklist/index.html | 836 ------
.../2.7/zh-cn/site/dev/code-smell/index.html | 962 -------
.../2.7/zh-cn/site/dev/coding/index.html | 866 ------
.../2.7/zh-cn/site/dev/contract/index.html | 820 ------
.../2.7/zh-cn/site/dev/contribution/index.html | 1127 --------
.../2.7/zh-cn/site/dev/design/index.html | 905 ------
.../2.7/zh-cn/site/dev/implementation/index.html | 975 -------
.../2.7/zh-cn/site/dev/impls/cache/index.html | 883 ------
.../2.7/zh-cn/site/dev/impls/cluster/index.html | 877 ------
.../2.7/zh-cn/site/dev/impls/compiler/index.html | 858 ------
.../zh-cn/site/dev/impls/config-center/index.html | 893 ------
.../2.7/zh-cn/site/dev/impls/container/index.html | 865 ------
.../2.7/zh-cn/site/dev/impls/dispatcher/index.html | 865 ------
.../2.7/zh-cn/site/dev/impls/exchanger/index.html | 890 ------
.../site/dev/impls/exporter-listener/index.html | 866 ------
.../site/dev/impls/extension-factory/index.html | 860 ------
.../2.7/zh-cn/site/dev/impls/filter/index.html | 892 ------
.../zh-cn/site/dev/impls/introduction/index.html | 778 -----
.../site/dev/impls/invoker-listener/index.html | 865 ------
.../zh-cn/site/dev/impls/load-balance/index.html | 866 ------
.../zh-cn/site/dev/impls/logger-adapter/index.html | 883 ------
.../2.7/zh-cn/site/dev/impls/merger/index.html | 862 ------
.../2.7/zh-cn/site/dev/impls/monitor/index.html | 876 ------
.../2.7/zh-cn/site/dev/impls/networker/index.html | 862 ------
.../2.7/zh-cn/site/dev/impls/page/index.html | 864 ------
.../2.7/zh-cn/site/dev/impls/protocol/index.html | 951 -------
.../zh-cn/site/dev/impls/proxy-factory/index.html | 868 ------
.../2.7/zh-cn/site/dev/impls/registry/index.html | 1001 -------
.../2.7/zh-cn/site/dev/impls/remoting/index.html | 923 ------
.../2.7/zh-cn/site/dev/impls/router/index.html | 861 ------
.../2.7/zh-cn/site/dev/impls/serialize/index.html | 877 ------
.../zh-cn/site/dev/impls/status-checker/index.html | 867 ------
.../zh-cn/site/dev/impls/telnet-handler/index.html | 880 ------
.../2.7/zh-cn/site/dev/impls/threadpool/index.html | 863 ------
.../2.7/zh-cn/site/dev/impls/validation/index.html | 874 ------
documentations/2.7/zh-cn/site/dev/index.html | 782 -----
.../2.7/zh-cn/site/dev/introduction/index.html | 777 -----
.../site/dev/principals/code-detail/index.html | 844 ------
.../site/dev/principals/configuration/index.html | 890 ------
.../2.7/zh-cn/site/dev/principals/dummy/index.html | 1002 -------
.../site/dev/principals/expansibility/index.html | 814 ------
.../zh-cn/site/dev/principals/extension/index.html | 911 ------
.../dev/principals/general-knowledge/index.html | 863 ------
.../site/dev/principals/introduction/index.html | 778 -----
.../site/dev/principals/robustness/index.html | 864 ------
.../2.7/zh-cn/site/dev/release/index.html | 841 ------
.../zh-cn/site/dev/sources/images/close-expand.jpg | Bin 19287 -> 0 bytes
.../dev/sources/images/configuration-override.png | Bin 11422 -> 0 bytes
.../2.7/zh-cn/site/dev/sources/images/ddd.jpg | Bin 19358 -> 0 bytes
.../zh-cn/site/dev/sources/images/design-step1.png | Bin 121672 -> 0 bytes
.../zh-cn/site/dev/sources/images/design-step2.png | Bin 141298 -> 0 bytes
.../zh-cn/site/dev/sources/images/design-step3.png | Bin 165828 -> 0 bytes
.../zh-cn/site/dev/sources/images/design-step4.png | Bin 240786 -> 0 bytes
.../zh-cn/site/dev/sources/images/dubbo-export.jpg | Bin 70132 -> 0 bytes
.../site/dev/sources/images/dubbo-extension.jpg | Bin 112692 -> 0 bytes
.../site/dev/sources/images/dubbo-framework.jpg | Bin 219759 -> 0 bytes
.../site/dev/sources/images/dubbo-modules.jpg | Bin 25411 -> 0 bytes
.../site/dev/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../zh-cn/site/dev/sources/images/dubbo-refer.jpg | Bin 105967 -> 0 bytes
.../site/dev/sources/images/dubbo-relation.jpg | Bin 30304 -> 0 bytes
.../dev/sources/images/dubbo_protocol_header.png | Bin 74833 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_export.jpg | Bin 47624 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_invoke.jpg | Bin 45874 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_refer.jpg | Bin 50211 -> 0 bytes
.../site/dev/sources/images/event-listener.jpg | Bin 13192 -> 0 bytes
.../zh-cn/site/dev/sources/images/filter-chain.jpg | Bin 41029 -> 0 bytes
.../zh-cn/site/dev/sources/images/mix-api-spi.jpg | Bin 17004 -> 0 bytes
.../zh-cn/site/dev/sources/images/open-expand.jpg | Bin 10549 -> 0 bytes
.../site/dev/sources/images/seperate-api-spi.jpg | Bin 23683 -> 0 bytes
.../apache-dubbo-page_dev/index.html | 792 ------
.../label-an-issue-guide_dev/index.html | 801 ------
.../new-committer-guide_dev/index.html | 843 ------
.../committer-guide/release-guide_dev/index.html | 1175 --------
.../committer-guide/website-guide_dev/index.html | 781 -----
.../become-a-committer_dev/index.html | 784 -----
.../cla-signing-guide_dev/index.html | 800 ------
.../dubbo-extension-guide_dev/index.html | 811 ------
.../mailing-list-subscription-guide_dev/index.html | 857 ------
.../new-contributor-guide_dev/index.html | 804 ------
.../reporting-security-issues_dev/index.html | 790 ------
.../software-donation-guide_dev/index.html | 888 ------
.../test-coverage-guide_dev/index.html | 797 ------
.../site/developers/developers_dev/index.html | 1109 --------
.../2.7/zh-cn/site/developers/guide_dev/index.html | 853 ------
.../site/developers/user-guide/faq_dev/index.html | 792 ------
.../2.7/zh-cn/site/fonts/fontawesome-webfont.eot | Bin 37405 -> 0 bytes
.../2.7/zh-cn/site/fonts/fontawesome-webfont.svg | 399 ---
.../2.7/zh-cn/site/fonts/fontawesome-webfont.ttf | Bin 79076 -> 0 bytes
.../2.7/zh-cn/site/fonts/fontawesome-webfont.woff | Bin 43572 -> 0 bytes
documentations/2.7/zh-cn/site/img/favicon.ico | Bin 1150 -> 0 bytes
documentations/2.7/zh-cn/site/index.html | 795 ------
.../2.7/zh-cn/site/js/jquery-2.1.1.min.js | 4 -
.../2.7/zh-cn/site/js/modernizr-2.8.3.min.js | 1 -
documentations/2.7/zh-cn/site/js/theme.js | 105 -
documentations/2.7/zh-cn/site/search.html | 776 -----
documentations/2.7/zh-cn/site/search/lunr.js | 2986 --------------------
documentations/2.7/zh-cn/site/search/main.js | 96 -
.../2.7/zh-cn/site/search/search_index.json | 1 -
documentations/2.7/zh-cn/site/search/worker.js | 128 -
documentations/2.7/zh-cn/site/sitemap.xml | 718 -----
documentations/2.7/zh-cn/site/sitemap.xml.gz | Bin 278 -> 0 bytes
.../adaptive-extension/index.html | 1473 ----------
.../site/source_code_guide/cluster/index.html | 1316 ---------
.../site/source_code_guide/directory/index.html | 1269 ---------
.../site/source_code_guide/dubbo-spi/index.html | 1152 --------
.../source_code_guide/export-service/index.html | 2169 --------------
.../site/source_code_guide/loadbalance/index.html | 1504 ----------
.../source_code_guide/refer-service/index.html | 1617 -----------
.../zh-cn/site/source_code_guide/router/index.html | 1220 --------
.../service-invoking-process/index.html | 2703 ------------------
.../source_code_guide/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../images/consistent-hash-data-incline.jpg | Bin 101943 -> 0 bytes
.../sources/images/consistent-hash-invoker.jpg | Bin 87844 -> 0 bytes
.../sources/images/consistent-hash.jpg | Bin 95740 -> 0 bytes
.../sources/images/data-format.jpg | Bin 115165 -> 0 bytes
.../sources/images/directory-inherit-hierarchy.png | Bin 69024 -> 0 bytes
.../sources/images/dispatcher-location.jpg | Bin 89871 -> 0 bytes
.../sources/images/dubbo-spi-result.jpg | Bin 33007 -> 0 bytes
.../sources/images/java-spi-result.jpg | Bin 46805 -> 0 bytes
.../sources/images/request-id-application.jpg | Bin 217379 -> 0 bytes
.../sources/images/send-request-process.jpg | Bin 83592 -> 0 bytes
.../sources/images/send-request-thread-stack.jpg | Bin 213679 -> 0 bytes
.../sources/images/service-registry.png | Bin 57116 -> 0 bytes
documentations/2.7/zh-cn/site/user/LICENSE | 201 --
.../2.7/zh-cn/site/user/SUMMARY/index.html | 901 ------
.../2.7/zh-cn/site/user/benchmark-tool/index.html | 804 ------
.../2.7/zh-cn/site/user/best-practice/index.html | 851 ------
.../2.7/zh-cn/site/user/capacity-plan/index.html | 823 ------
.../site/user/configuration/annotation/index.html | 882 ------
.../zh-cn/site/user/configuration/api/index.html | 922 ------
.../user/configuration/config-center/index.html | 884 ------
.../configuration-load-process/index.html | 970 -------
.../configuration/environment-variables/index.html | 841 ------
.../2.7/zh-cn/site/user/configuration/index.html | 782 -----
.../configuration/properties-deprecated/index.html | 803 ------
.../site/user/configuration/properties/index.html | 806 ------
.../zh-cn/site/user/configuration/xml/index.html | 940 ------
.../2.7/zh-cn/site/user/coveragence/index.html | 787 ------
.../demos/GooglePb-generic-reference/index.html | 856 ------
.../2.7/zh-cn/site/user/demos/accesslog/index.html | 812 ------
.../user/demos/async-call-deprecated/index.html | 822 ------
.../zh-cn/site/user/demos/async-call/index.html | 912 ------
.../demos/async-execute-on-provider/index.html | 881 ------
.../zh-cn/site/user/demos/attachment/index.html | 832 ------
.../2.7/zh-cn/site/user/demos/auth/index.html | 799 ------
.../site/user/demos/callback-parameter/index.html | 914 ------
.../site/user/demos/concurrency-control/index.html | 856 ------
.../site/user/demos/config-connections/index.html | 798 ------
.../user/demos/config-rule-deprecated/index.html | 814 ------
.../zh-cn/site/user/demos/config-rule/index.html | 991 -------
.../site/user/demos/consumer-threadpool/index.html | 806 ------
.../2.7/zh-cn/site/user/demos/context/index.html | 844 ------
.../zh-cn/site/user/demos/delay-publish/index.html | 853 ------
.../user/demos/distributed-transaction/index.html | 807 ------
.../2.7/zh-cn/site/user/demos/dump/index.html | 815 ------
.../zh-cn/site/user/demos/echo-service/index.html | 821 ------
.../zh-cn/site/user/demos/events-notify/index.html | 901 ------
.../site/user/demos/explicit-target/index.html | 839 ------
.../user/demos/fault-tolerent-strategy/index.html | 860 ------
.../site/user/demos/generic-reference/index.html | 894 ------
.../site/user/demos/generic-service/index.html | 847 ------
.../site/user/demos/graceful-shutdown/index.html | 833 ------
.../zh-cn/site/user/demos/group-merger/index.html | 846 ------
.../site/user/demos/hostname-binding/index.html | 891 ------
.../2.7/zh-cn/site/user/demos/index.html | 782 -----
.../zh-cn/site/user/demos/introduction/index.html | 780 -----
.../zh-cn/site/user/demos/lazy-connect/index.html | 809 ------
.../zh-cn/site/user/demos/loadbalance/index.html | 858 ------
.../zh-cn/site/user/demos/local-call/index.html | 841 ------
.../zh-cn/site/user/demos/local-mock/index.html | 879 ------
.../zh-cn/site/user/demos/local-stub/index.html | 838 ------
.../site/user/demos/logger-strategy/index.html | 822 ------
.../site/user/demos/multi-protocols/index.html | 848 ------
.../site/user/demos/multi-registry/index.html | 880 ------
.../site/user/demos/multi-versions/index.html | 832 ------
.../2.7/zh-cn/site/user/demos/netty4/index.html | 829 ------
.../user/demos/parameter-validation/index.html | 977 -------
.../site/user/demos/preflight-check/index.html | 847 ------
.../zh-cn/site/user/demos/protobuf-idl/index.html | 804 ------
.../user/demos/reference-config-cache/index.html | 802 ------
.../zh-cn/site/user/demos/registry-only/index.html | 814 ------
.../zh-cn/site/user/demos/result-cache/index.html | 831 ------
.../user/demos/routing-rule-deprecated/index.html | 925 ------
.../zh-cn/site/user/demos/routing-rule/index.html | 1036 -------
.../zh-cn/site/user/demos/serialization/index.html | 876 ------
.../site/user/demos/service-container/index.html | 861 ------
.../site/user/demos/service-downgrade/index.html | 817 ------
.../zh-cn/site/user/demos/service-group/index.html | 828 ------
.../2.7/zh-cn/site/user/demos/set-host/index.html | 832 ------
.../user/demos/simplify-registry-data/index.html | 1125 --------
.../site/user/demos/static-service/index.html | 818 ------
.../zh-cn/site/user/demos/stickiness/index.html | 814 ------
.../site/user/demos/subscribe-only/index.html | 814 ------
.../zh-cn/site/user/demos/thread-model/index.html | 827 ------
.../2.7/zh-cn/site/user/demos/tls/index.html | 809 ------
.../site/user/demos/token-authorization/index.html | 825 ------
.../2.7/zh-cn/site/user/dependencies/index.html | 858 ------
documentations/2.7/zh-cn/site/user/index.html | 783 -----
.../user/languages/erlang/reference/index.html | 790 ------
.../user/languages/erlang/serialization/index.html | 805 ------
.../site/user/languages/erlang/service/index.html | 820 ------
.../site/user/languages/erlang/start/index.html | 824 ------
.../2.7/zh-cn/site/user/maturity/index.html | 1412 ---------
.../site/user/new-features-in-a-glance/index.html | 901 ------
.../2.7/zh-cn/site/user/perf-test/index.html | 998 -------
.../site/user/preface/architecture/index.html | 925 ------
.../zh-cn/site/user/preface/background/index.html | 826 ------
.../2.7/zh-cn/site/user/preface/index.html | 782 -----
.../site/user/preface/requirements/index.html | 783 -----
.../2.7/zh-cn/site/user/preface/usage/index.html | 841 ------
.../2.7/zh-cn/site/user/quick-start/index.html | 911 ------
.../2.7/zh-cn/site/user/recommend/index.html | 947 -------
.../2.7/zh-cn/site/user/references/api/index.html | 821 ------
.../zh-cn/site/user/references/maven/index.html | 819 ------
.../references/metadata/introduction/index.html | 1087 -------
.../references/metadata/metadata-redis/index.html | 804 ------
.../metadata/metadata-zookeeper/index.html | 804 ------
.../site/user/references/protocol/dubbo/index.html | 929 ------
.../site/user/references/protocol/gRPC/index.html | 791 ------
.../user/references/protocol/hessian/index.html | 868 ------
.../site/user/references/protocol/http/index.html | 860 ------
.../references/protocol/introduction/index.html | 778 -----
.../user/references/protocol/memcached/index.html | 806 ------
.../site/user/references/protocol/redis/index.html | 806 ------
.../site/user/references/protocol/rest/index.html | 1379 ---------
.../site/user/references/protocol/rmi/index.html | 883 ------
.../user/references/protocol/thrift/index.html | 839 ------
.../user/references/protocol/webservice/index.html | 863 ------
.../2.7/zh-cn/site/user/references/qos/index.html | 1019 -------
.../references/registry/introduction/index.html | 778 -----
.../user/references/registry/multicast/index.html | 836 ------
.../site/user/references/registry/nacos/index.html | 858 ------
.../site/user/references/registry/redis/index.html | 873 ------
.../user/references/registry/simple/index.html | 848 ------
.../user/references/registry/zookeeper/index.html | 919 ------
.../zh-cn/site/user/references/telnet/index.html | 896 ------
.../references/xml/dubbo-application/index.html | 901 ------
.../user/references/xml/dubbo-argument/index.html | 856 ------
.../references/xml/dubbo-config-center/index.html | 937 ------
.../user/references/xml/dubbo-consumer/index.html | 1001 -------
.../user/references/xml/dubbo-method/index.html | 986 -------
.../user/references/xml/dubbo-module/index.html | 861 ------
.../user/references/xml/dubbo-monitor/index.html | 841 ------
.../user/references/xml/dubbo-parameter/index.html | 850 ------
.../user/references/xml/dubbo-protocol/index.html | 1061 -------
.../user/references/xml/dubbo-provider/index.html | 1261 ---------
.../user/references/xml/dubbo-reference/index.html | 1091 -------
.../user/references/xml/dubbo-registry/index.html | 1001 -------
.../user/references/xml/dubbo-service/index.html | 1131 --------
.../user/references/xml/introduction/index.html | 788 ------
documentations/2.7/zh-cn/site/user/rest/index.html | 1776 ------------
.../2.7/zh-cn/site/user/serialization/index.html | 1041 -------
.../2.7/zh-cn/site/user/simple-monitor/index.html | 841 ------
.../2.7/zh-cn/site/user/sources/images/1kres.png | Bin 39384 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/1ktps.png | Bin 38814 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/200kres.png | Bin 39229 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/200ktps.png | Bin 38997 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/50kres.png | Bin 39733 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/50ktps.png | Bin 39723 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/arch.png | Bin 15546 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../site/user/sources/images/code-coverage.jpg | Bin 141776 -> 0 bytes
.../site/user/sources/images/code-dependency.jpg | Bin 138868 -> 0 bytes
.../site/user/sources/images/code-quality1.jpg | Bin 56913 -> 0 bytes
.../site/user/sources/images/code-quality5.jpg | Bin 41672 -> 0 bytes
.../site/user/sources/images/code-tendency.jpg | Bin 54729 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/context.png | Bin 46114 -> 0 bytes
.../sources/images/dubbo-architecture-future.jpg | Bin 55605 -> 0 bytes
.../sources/images/dubbo-architecture-roadmap.jpg | Bin 33931 -> 0 bytes
.../user/sources/images/dubbo-architecture.jpg | Bin 18810 -> 0 bytes
.../user/sources/images/dubbo-config-override.jpg | Bin 68132 -> 0 bytes
.../site/user/sources/images/dubbo-config.jpg | Bin 69630 -> 0 bytes
.../site/user/sources/images/dubbo-directly.jpg | Bin 38922 -> 0 bytes
.../sources/images/dubbo-properties-override.jpg | Bin 24590 -> 0 bytes
.../site/user/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../user/sources/images/dubbo-redis-registry.jpg | Bin 47205 -> 0 bytes
.../sources/images/dubbo-service-governance.jpg | Bin 67000 -> 0 bytes
.../zh-cn/site/user/sources/images/dubbo-token.jpg | Bin 17153 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/future.jpg | Bin 20793 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/jta-xa.jpg | Bin 37931 -> 0 bytes
.../site/user/sources/images/lock-get-bean.jpg | Bin 109801 -> 0 bytes
.../site/user/sources/images/lock-init-context.jpg | Bin 39227 -> 0 bytes
.../zh-cn/site/user/sources/images/multicast.jpg | Bin 20269 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/pojores.png | Bin 37733 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/pojotps.png | Bin 39797 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/rest.jpg | Bin 206610 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/rt.png | Bin 31098 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/stub.jpg | Bin 28646 -> 0 bytes
.../site/user/sources/images/subscribe-only.jpg | Bin 20626 -> 0 bytes
...pg-version=1&modificationDate=1326468174000.jpg | Bin 20626 -> 0 bytes
.../2.7/zh-cn/site/user/sources/images/tps.png | Bin 33114 -> 0 bytes
.../zh-cn/site/user/sources/images/zookeeper.jpg | Bin 31272 -> 0 bytes
.../2.7/zh-cn/site/user/versions/index.html | 783 -----
.../site/user/versions/version-270/index.html | 1095 -------
documentations/3.0/en-us/docs/admin/README.md | 3 -
documentations/3.0/en-us/docs/admin/SUMMARY.md | 4 -
.../3.0/en-us/docs/admin/install/admin-console.md | 40 -
.../3.0/en-us/docs/admin/install/consumer-demo.md | 20 -
.../3.0/en-us/docs/admin/install/introduction.md | 13 -
.../3.0/en-us/docs/admin/install/provider-demo.md | 18 -
.../3.0/en-us/docs/admin/install/redis.md | 54 -
.../docs/admin/install/simple-monitor-center.md | 3 -
.../docs/admin/install/simple-registry-center.md | 1 -
.../3.0/en-us/docs/admin/install/zookeeper.md | 98 -
.../3.0/en-us/docs/admin/introduction.md | 65 -
.../3.0/en-us/docs/admin/ops/dubbo-ops.md | 26 -
.../3.0/en-us/docs/admin/ops/introduction.md | 1 -
.../3.0/en-us/docs/admin/ops/pinpoint.md | 411 ---
.../3.0/en-us/docs/admin/ops/skywalking.md | 121 -
.../3.0/en-us/docs/admin/serviceGovernance.md | 46 -
.../3.0/en-us/docs/admin/serviceSearch.md | 7 -
documentations/3.0/en-us/docs/admin/serviceTest.md | 1 -
.../en-us/docs/admin/sources/images/blackList.jpg | Bin 99079 -> 0 bytes
.../3.0/en-us/docs/admin/sources/images/check.gif | Bin 604 -> 0 bytes
.../3.0/en-us/docs/admin/sources/images/config.jpg | Bin 137909 -> 0 bytes
.../3.0/en-us/docs/admin/sources/images/detail.jpg | Bin 188392 -> 0 bytes
.../docs/admin/sources/images/dubbo-add-config.jpg | Bin 303596 -> 0 bytes
.../docs/admin/sources/images/dubbo-add-route.jpg | Bin 330146 -> 0 bytes
.../admin/sources/images/dubbo-applications.png | Bin 93036 -> 0 bytes
.../docs/admin/sources/images/dubbo-consumers.jpg | Bin 274307 -> 0 bytes
.../admin/sources/images/dubbo-monitor-simple.jpg | Bin 87670 -> 0 bytes
.../docs/admin/sources/images/dubbo-providers.jpg | Bin 272674 -> 0 bytes
.../docs/admin/sources/images/dubbo-search.jpg | Bin 224751 -> 0 bytes
.../admin/sources/images/pinpoint-calltree.png | Bin 655223 -> 0 bytes
.../docs/admin/sources/images/pinpoint-home.png | Bin 303613 -> 0 bytes
.../admin/sources/images/pinpoint-mixedview.png | Bin 434638 -> 0 bytes
.../docs/admin/sources/images/searchResult.png | Bin 168461 -> 0 bytes
.../docs/admin/sources/images/skywalking-alarm.png | Bin 181739 -> 0 bytes
.../sources/images/skywalking-application.png | Bin 229539 -> 0 bytes
.../images/skywalking-application_instance.png | Bin 203651 -> 0 bytes
.../admin/sources/images/skywalking-dashboard.png | Bin 257273 -> 0 bytes
.../sources/images/skywalking-service-consumer.png | Bin 282541 -> 0 bytes
.../sources/images/skywalking-service-provider.png | Bin 366038 -> 0 bytes
.../admin/sources/images/skywalking-span-Info.png | Bin 192403 -> 0 bytes
.../admin/sources/images/skywalking-topology.png | Bin 173667 -> 0 bytes
.../docs/admin/sources/images/skywalking-trace.png | Bin 217096 -> 0 bytes
.../3.0/en-us/docs/admin/sources/images/tip.png | Bin 876 -> 0 bytes
.../en-us/docs/admin/sources/images/warning-3.gif | Bin 569 -> 0 bytes
.../3.0/en-us/docs/admin/sources/images/weight.jpg | Bin 89265 -> 0 bytes
documentations/3.0/en-us/docs/dev/LICENSE | 201 --
documentations/3.0/en-us/docs/dev/README.md | 3 -
documentations/3.0/en-us/docs/dev/SPI.md | 237 --
documentations/3.0/en-us/docs/dev/SUMMARY.md | 41 -
documentations/3.0/en-us/docs/dev/TCK.md | 19 -
documentations/3.0/en-us/docs/dev/build.md | 81 -
documentations/3.0/en-us/docs/dev/checklist.md | 19 -
documentations/3.0/en-us/docs/dev/code-smell.md | 205 --
documentations/3.0/en-us/docs/dev/coding.md | 53 -
documentations/3.0/en-us/docs/dev/contract.md | 14 -
documentations/3.0/en-us/docs/dev/contribution.md | 89 -
documentations/3.0/en-us/docs/dev/design.md | 99 -
.../3.0/en-us/docs/dev/implementation.md | 155 -
documentations/3.0/en-us/docs/dev/impls/cache.md | 84 -
documentations/3.0/en-us/docs/dev/impls/cluster.md | 74 -
.../3.0/en-us/docs/dev/impls/compiler.md | 55 -
.../3.0/en-us/docs/dev/impls/config-center.md | 96 -
.../3.0/en-us/docs/dev/impls/container.md | 62 -
.../3.0/en-us/docs/dev/impls/dispatcher.md | 62 -
.../3.0/en-us/docs/dev/impls/exchanger.md | 91 -
.../3.0/en-us/docs/dev/impls/exporter-listener.md | 66 -
.../3.0/en-us/docs/dev/impls/extension-factory.md | 57 -
documentations/3.0/en-us/docs/dev/impls/filter.md | 89 -
.../3.0/en-us/docs/dev/impls/introduction.md | 3 -
.../3.0/en-us/docs/dev/impls/invoker-listener.md | 65 -
.../3.0/en-us/docs/dev/impls/load-balance.md | 63 -
.../3.0/en-us/docs/dev/impls/logger-adapter.md | 84 -
documentations/3.0/en-us/docs/dev/impls/merger.md | 60 -
documentations/3.0/en-us/docs/dev/impls/monitor.md | 75 -
.../3.0/en-us/docs/dev/impls/networker.md | 59 -
documentations/3.0/en-us/docs/dev/impls/page.md | 61 -
.../3.0/en-us/docs/dev/impls/protocol.md | 150 -
.../3.0/en-us/docs/dev/impls/proxy-factory.md | 65 -
.../3.0/en-us/docs/dev/impls/registry.md | 207 --
.../3.0/en-us/docs/dev/impls/remoting.md | 122 -
documentations/3.0/en-us/docs/dev/impls/router.md | 58 -
.../3.0/en-us/docs/dev/impls/serialize.md | 72 -
.../3.0/en-us/docs/dev/impls/status-checker.md | 64 -
.../3.0/en-us/docs/dev/impls/telnet-handler.md | 77 -
.../3.0/en-us/docs/dev/impls/threadpool.md | 61 -
.../3.0/en-us/docs/dev/impls/validation.md | 75 -
documentations/3.0/en-us/docs/dev/introduction.md | 0
.../3.0/en-us/docs/dev/principals/code-detail.md | 36 -
.../3.0/en-us/docs/dev/principals/configuration.md | 83 -
.../3.0/en-us/docs/dev/principals/dummy.md | 203 --
.../3.0/en-us/docs/dev/principals/expansibility.md | 18 -
.../3.0/en-us/docs/dev/principals/extension.md | 135 -
.../en-us/docs/dev/principals/general-knowledge.md | 68 -
.../3.0/en-us/docs/dev/principals/introduction.md | 3 -
.../3.0/en-us/docs/dev/principals/robustness.md | 83 -
documentations/3.0/en-us/docs/dev/release.md | 34 -
.../en-us/docs/dev/sources/images/close-expand.jpg | Bin 19287 -> 0 bytes
.../dev/sources/images/configuration-override.png | Bin 11422 -> 0 bytes
.../3.0/en-us/docs/dev/sources/images/ddd.jpg | Bin 19358 -> 0 bytes
.../en-us/docs/dev/sources/images/design-step1.png | Bin 121672 -> 0 bytes
.../en-us/docs/dev/sources/images/design-step2.png | Bin 141298 -> 0 bytes
.../en-us/docs/dev/sources/images/design-step3.png | Bin 165828 -> 0 bytes
.../en-us/docs/dev/sources/images/design-step4.png | Bin 240786 -> 0 bytes
.../en-us/docs/dev/sources/images/dubbo-export.jpg | Bin 70132 -> 0 bytes
.../docs/dev/sources/images/dubbo-extension.jpg | Bin 112692 -> 0 bytes
.../docs/dev/sources/images/dubbo-framework.jpg | Bin 219759 -> 0 bytes
.../docs/dev/sources/images/dubbo-modules.jpg | Bin 25411 -> 0 bytes
.../docs/dev/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../en-us/docs/dev/sources/images/dubbo-refer.jpg | Bin 105967 -> 0 bytes
.../docs/dev/sources/images/dubbo-relation.jpg | Bin 30304 -> 0 bytes
.../dev/sources/images/dubbo_protocol_header.png | Bin 74833 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_export.jpg | Bin 47624 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_invoke.jpg | Bin 45874 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_refer.jpg | Bin 50211 -> 0 bytes
.../docs/dev/sources/images/event-listener.jpg | Bin 13192 -> 0 bytes
.../en-us/docs/dev/sources/images/filter-chain.jpg | Bin 41029 -> 0 bytes
.../en-us/docs/dev/sources/images/mix-api-spi.jpg | Bin 17004 -> 0 bytes
.../en-us/docs/dev/sources/images/open-expand.jpg | Bin 10549 -> 0 bytes
.../docs/dev/sources/images/seperate-api-spi.jpg | Bin 23683 -> 0 bytes
.../committer-guide/apache-dubbo-page_dev.md | 33 -
.../committer-guide/label-an-issue-guide_dev.md | 29 -
.../committer-guide/new-committer-guide_dev.md | 95 -
.../committer-guide/release-guide_dev.md | 500 ----
.../committer-guide/website-guide_dev.md | 4 -
.../contributor-guide/become-a-committer_dev.md | 15 -
.../contributor-guide/cla-signing-guide_dev.md | 25 -
.../contributor-guide/dubbo-extension-guide_dev.md | 37 -
.../mailing-list-subscription-guide_dev.md | 80 -
.../contributor-guide/new-contributor-guide_dev.md | 62 -
.../reporting-security-issues_dev.md | 21 -
.../software-donation-guide_dev.md | 106 -
.../contributor-guide/test-coverage-guide_dev.md | 16 -
.../3.0/en-us/docs/developers/developers_dev.md | 57 -
.../3.0/en-us/docs/developers/guide_dev.md | 76 -
.../en-us/docs/developers/user-guide/faq_dev.md | 27 -
documentations/3.0/en-us/docs/index.md | 25 -
documentations/3.0/en-us/docs/user/LICENSE | 201 --
documentations/3.0/en-us/docs/user/README.md | 3 -
documentations/3.0/en-us/docs/user/SUMMARY.md | 94 -
.../3.0/en-us/docs/user/benchmark-tool.md | 34 -
.../3.0/en-us/docs/user/best-practice.md | 63 -
.../3.0/en-us/docs/user/capacity-plan.md | 17 -
.../en-us/docs/user/configuration/annotation.md | 94 -
.../3.0/en-us/docs/user/configuration/api.md | 119 -
.../configuration/configuration-load-process.md | 180 --
.../3.0/en-us/docs/user/configuration/index.md | 1 -
.../en-us/docs/user/configuration/properties.md | 43 -
.../3.0/en-us/docs/user/configuration/xml.md | 77 -
documentations/3.0/en-us/docs/user/coveragence.md | 24 -
.../3.0/en-us/docs/user/demos/accesslog.md | 57 -
.../en-us/docs/user/demos/async-call-deprecated.md | 59 -
.../3.0/en-us/docs/user/demos/async-call.md | 59 -
.../docs/user/demos/async-execute-on-provider.md | 90 -
.../3.0/en-us/docs/user/demos/attachment.md | 27 -
.../en-us/docs/user/demos/callback-parameter.md | 110 -
.../en-us/docs/user/demos/concurrency-control.md | 60 -
.../en-us/docs/user/demos/config-connections.md | 30 -
.../docs/user/demos/config-rule-deprecated.md | 47 -
.../3.0/en-us/docs/user/demos/config-rule.md | 47 -
.../3.0/en-us/docs/user/demos/context.md | 39 -
.../3.0/en-us/docs/user/demos/delay-publish.md | 50 -
.../docs/user/demos/distributed-transaction.md | 7 -
documentations/3.0/en-us/docs/user/demos/dump.md | 19 -
.../3.0/en-us/docs/user/demos/echo-service.md | 25 -
.../3.0/en-us/docs/user/demos/events-notify.md | 95 -
.../3.0/en-us/docs/user/demos/explicit-target.md | 37 -
.../docs/user/demos/fault-tolerent-strategy.md | 75 -
.../3.0/en-us/docs/user/demos/generic-reference.md | 97 -
.../3.0/en-us/docs/user/demos/generic-service.md | 45 -
.../3.0/en-us/docs/user/demos/graceful-shutdown.md | 30 -
.../3.0/en-us/docs/user/demos/group-merger.md | 54 -
.../3.0/en-us/docs/user/demos/hostname-binding.md | 58 -
documentations/3.0/en-us/docs/user/demos/index.md | 1 -
.../3.0/en-us/docs/user/demos/introduction.md | 2 -
.../3.0/en-us/docs/user/demos/lazy-connect.md | 9 -
.../3.0/en-us/docs/user/demos/loadbalance.md | 64 -
.../3.0/en-us/docs/user/demos/local-call.md | 48 -
.../3.0/en-us/docs/user/demos/local-mock.md | 100 -
.../3.0/en-us/docs/user/demos/local-stub.md | 47 -
.../3.0/en-us/docs/user/demos/logger-strategy.md | 23 -
.../3.0/en-us/docs/user/demos/multi-protocols.md | 45 -
.../3.0/en-us/docs/user/demos/multi-registry.md | 83 -
.../3.0/en-us/docs/user/demos/multi-versions.md | 42 -
documentations/3.0/en-us/docs/user/demos/netty4.md | 35 -
.../en-us/docs/user/demos/parameter-validation.md | 183 --
.../3.0/en-us/docs/user/demos/preflight-check.md | 56 -
.../docs/user/demos/reference-config-cache.md | 38 -
.../3.0/en-us/docs/user/demos/registry-only.md | 19 -
.../3.0/en-us/docs/user/demos/result-cache.md | 28 -
.../3.0/en-us/docs/user/demos/routing-rule.md | 193 --
.../3.0/en-us/docs/user/demos/serialization.md | 77 -
.../3.0/en-us/docs/user/demos/service-container.md | 61 -
.../3.0/en-us/docs/user/demos/service-downgrade.md | 19 -
.../3.0/en-us/docs/user/demos/service-group.md | 27 -
.../3.0/en-us/docs/user/demos/static-service.md | 27 -
.../3.0/en-us/docs/user/demos/stickiness.md | 17 -
.../3.0/en-us/docs/user/demos/subscribe-only.md | 19 -
.../3.0/en-us/docs/user/demos/thread-model.md | 34 -
.../en-us/docs/user/demos/token-authorization.md | 46 -
documentations/3.0/en-us/docs/user/dependencies.md | 58 -
.../en-us/docs/user/languages/erlang/reference.md | 15 -
.../docs/user/languages/erlang/serialization.md | 17 -
.../en-us/docs/user/languages/erlang/service.md | 22 -
.../3.0/en-us/docs/user/languages/erlang/start.md | 62 -
documentations/3.0/en-us/docs/user/maturity.md | 93 -
documentations/3.0/en-us/docs/user/perf-test.md | 168 --
.../3.0/en-us/docs/user/preface/architecture.md | 66 -
.../3.0/en-us/docs/user/preface/background.md | 21 -
.../3.0/en-us/docs/user/preface/index.md | 1 -
.../3.0/en-us/docs/user/preface/requirements.md | 13 -
.../3.0/en-us/docs/user/preface/usage.md | 39 -
documentations/3.0/en-us/docs/user/quick-start.md | 252 --
documentations/3.0/en-us/docs/user/recommend.md | 169 --
.../3.0/en-us/docs/user/references/api.md | 63 -
.../3.0/en-us/docs/user/references/maven.md | 19 -
.../docs/user/references/metadata/introduction.md | 369 ---
.../en-us/docs/user/references/protocol/dubbo.md | 110 -
.../en-us/docs/user/references/protocol/hessian.md | 70 -
.../en-us/docs/user/references/protocol/http.md | 58 -
.../docs/user/references/protocol/introduction.md | 5 -
.../docs/user/references/protocol/memcached.md | 42 -
.../en-us/docs/user/references/protocol/redis.md | 42 -
.../en-us/docs/user/references/protocol/rest.md | 741 -----
.../3.0/en-us/docs/user/references/protocol/rmi.md | 82 -
.../en-us/docs/user/references/protocol/thrift.md | 32 -
.../docs/user/references/protocol/webservice.md | 113 -
.../3.0/en-us/docs/user/references/qos.md | 227 --
.../docs/user/references/registry/introduction.md | 3 -
.../docs/user/references/registry/multicast.md | 38 -
.../en-us/docs/user/references/registry/nacos.md | 122 -
.../en-us/docs/user/references/registry/redis.md | 73 -
.../en-us/docs/user/references/registry/simple.md | 49 -
.../docs/user/references/registry/zookeeper.md | 154 -
.../3.0/en-us/docs/user/references/telnet.md | 104 -
.../docs/user/references/xml/dubbo-application.md | 14 -
.../docs/user/references/xml/dubbo-argument.md | 14 -
.../user/references/xml/dubbo-config-center.md | 19 -
.../docs/user/references/xml/dubbo-consumer.md | 24 -
.../en-us/docs/user/references/xml/dubbo-method.md | 30 -
.../en-us/docs/user/references/xml/dubbo-module.md | 10 -
.../docs/user/references/xml/dubbo-monitor.md | 8 -
.../docs/user/references/xml/dubbo-parameter.md | 22 -
.../docs/user/references/xml/dubbo-protocol.md | 30 -
.../docs/user/references/xml/dubbo-provider.md | 50 -
.../docs/user/references/xml/dubbo-reference.md | 39 -
.../docs/user/references/xml/dubbo-registry.md | 30 -
.../docs/user/references/xml/dubbo-service.md | 37 -
.../en-us/docs/user/references/xml/introduction.md | 16 -
documentations/3.0/en-us/docs/user/rest.md | 1227 --------
.../3.0/en-us/docs/user/simple-monitor.md | 84 -
.../3.0/en-us/docs/user/sources/images/1kres.png | Bin 39384 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/1ktps.png | Bin 38814 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/200kres.png | Bin 39229 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/200ktps.png | Bin 38997 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/50kres.png | Bin 39733 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/50ktps.png | Bin 39723 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/arch.png | Bin 15546 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../docs/user/sources/images/code-coverage.jpg | Bin 141776 -> 0 bytes
.../docs/user/sources/images/code-dependency.jpg | Bin 138868 -> 0 bytes
.../docs/user/sources/images/code-quality1.jpg | Bin 56913 -> 0 bytes
.../docs/user/sources/images/code-quality2.jpg | Bin 56913 -> 0 bytes
.../docs/user/sources/images/code-quality3.jpg | Bin 56913 -> 0 bytes
.../docs/user/sources/images/code-quality4.jpg | Bin 56913 -> 0 bytes
.../docs/user/sources/images/code-quality5.jpg | Bin 41672 -> 0 bytes
.../docs/user/sources/images/code-quality6.jpg | Bin 41672 -> 0 bytes
.../docs/user/sources/images/code-quality7.jpg | Bin 41672 -> 0 bytes
.../docs/user/sources/images/code-tendency.jpg | Bin 54729 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/context.png | Bin 46114 -> 0 bytes
.../sources/images/dubbo-architecture-future.jpg | Bin 55605 -> 0 bytes
.../sources/images/dubbo-architecture-roadmap.jpg | Bin 33931 -> 0 bytes
.../user/sources/images/dubbo-architecture.jpg | Bin 18810 -> 0 bytes
.../user/sources/images/dubbo-config-override.jpg | Bin 68132 -> 0 bytes
.../docs/user/sources/images/dubbo-config.jpg | Bin 69630 -> 0 bytes
.../docs/user/sources/images/dubbo-directly.jpg | Bin 38922 -> 0 bytes
.../sources/images/dubbo-properties-override.jpg | Bin 24590 -> 0 bytes
.../docs/user/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../user/sources/images/dubbo-redis-registry.jpg | Bin 47205 -> 0 bytes
.../sources/images/dubbo-service-governance.jpg | Bin 67000 -> 0 bytes
.../en-us/docs/user/sources/images/dubbo-token.jpg | Bin 17153 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/future.jpg | Bin 20793 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/jta-xa.jpg | Bin 37931 -> 0 bytes
.../docs/user/sources/images/lock-get-bean.jpg | Bin 109801 -> 0 bytes
.../docs/user/sources/images/lock-init-context.jpg | Bin 39227 -> 0 bytes
.../en-us/docs/user/sources/images/multicast.jpg | Bin 20269 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/pojores.png | Bin 37733 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/pojotps.png | Bin 39797 -> 0 bytes
.../3.0/en-us/docs/user/sources/images/stub.jpg | Bin 28646 -> 0 bytes
.../docs/user/sources/images/subscribe-only.jpg | Bin 20626 -> 0 bytes
...pg-version=1&modificationDate=1326468174000.jpg | Bin 20626 -> 0 bytes
.../en-us/docs/user/sources/images/zookeeper.jpg | Bin 31272 -> 0 bytes
documentations/3.0/en-us/mkdocs.yml | 155 -
documentations/3.0/en-us/site/404.html | 701 -----
.../3.0/en-us/site/admin/SUMMARY/index.html | 716 -----
documentations/3.0/en-us/site/admin/index.html | 714 -----
.../site/admin/install/admin-console/index.html | 736 -----
.../site/admin/install/consumer-demo/index.html | 722 -----
.../site/admin/install/introduction/index.html | 715 -----
.../site/admin/install/provider-demo/index.html | 721 -----
.../3.0/en-us/site/admin/install/redis/index.html | 746 -----
.../admin/install/simple-monitor-center/index.html | 710 -----
.../install/simple-registry-center/index.html | 709 -----
.../en-us/site/admin/install/zookeeper/index.html | 778 -----
.../3.0/en-us/site/admin/introduction/index.html | 805 ------
.../3.0/en-us/site/admin/ops/dubbo-ops/index.html | 720 -----
.../en-us/site/admin/ops/introduction/index.html | 709 -----
.../3.0/en-us/site/admin/ops/pinpoint/index.html | 1092 -------
.../3.0/en-us/site/admin/ops/skywalking/index.html | 808 ------
.../en-us/site/admin/serviceGovernance/index.html | 777 -----
.../3.0/en-us/site/admin/serviceSearch/index.html | 736 -----
.../3.0/en-us/site/admin/serviceTest/index.html | 725 -----
.../en-us/site/admin/sources/images/blackList.jpg | Bin 99079 -> 0 bytes
.../3.0/en-us/site/admin/sources/images/check.gif | Bin 604 -> 0 bytes
.../3.0/en-us/site/admin/sources/images/config.jpg | Bin 137909 -> 0 bytes
.../3.0/en-us/site/admin/sources/images/detail.jpg | Bin 188392 -> 0 bytes
.../site/admin/sources/images/dubbo-add-config.jpg | Bin 303596 -> 0 bytes
.../site/admin/sources/images/dubbo-add-route.jpg | Bin 330146 -> 0 bytes
.../admin/sources/images/dubbo-applications.png | Bin 93036 -> 0 bytes
.../site/admin/sources/images/dubbo-consumers.jpg | Bin 274307 -> 0 bytes
.../admin/sources/images/dubbo-monitor-simple.jpg | Bin 87670 -> 0 bytes
.../site/admin/sources/images/dubbo-providers.jpg | Bin 272674 -> 0 bytes
.../site/admin/sources/images/dubbo-search.jpg | Bin 224751 -> 0 bytes
.../admin/sources/images/pinpoint-calltree.png | Bin 655223 -> 0 bytes
.../site/admin/sources/images/pinpoint-home.png | Bin 303613 -> 0 bytes
.../admin/sources/images/pinpoint-mixedview.png | Bin 434638 -> 0 bytes
.../site/admin/sources/images/searchResult.png | Bin 168461 -> 0 bytes
.../site/admin/sources/images/skywalking-alarm.png | Bin 181739 -> 0 bytes
.../sources/images/skywalking-application.png | Bin 229539 -> 0 bytes
.../images/skywalking-application_instance.png | Bin 203651 -> 0 bytes
.../admin/sources/images/skywalking-dashboard.png | Bin 257273 -> 0 bytes
.../sources/images/skywalking-service-consumer.png | Bin 282541 -> 0 bytes
.../sources/images/skywalking-service-provider.png | Bin 366038 -> 0 bytes
.../admin/sources/images/skywalking-span-Info.png | Bin 192403 -> 0 bytes
.../admin/sources/images/skywalking-topology.png | Bin 173667 -> 0 bytes
.../site/admin/sources/images/skywalking-trace.png | Bin 217096 -> 0 bytes
.../3.0/en-us/site/admin/sources/images/tip.png | Bin 876 -> 0 bytes
.../en-us/site/admin/sources/images/warning-3.gif | Bin 569 -> 0 bytes
.../3.0/en-us/site/admin/sources/images/weight.jpg | Bin 89265 -> 0 bytes
documentations/3.0/en-us/site/css/theme.css | 12 -
documentations/3.0/en-us/site/css/theme_extra.css | 197 --
documentations/3.0/en-us/site/dev/LICENSE | 201 --
documentations/3.0/en-us/site/dev/SPI/index.html | 916 ------
.../3.0/en-us/site/dev/SUMMARY/index.html | 751 -----
documentations/3.0/en-us/site/dev/TCK/index.html | 753 -----
documentations/3.0/en-us/site/dev/build/index.html | 796 ------
.../3.0/en-us/site/dev/checklist/index.html | 758 -----
.../3.0/en-us/site/dev/code-smell/index.html | 894 ------
.../3.0/en-us/site/dev/coding/index.html | 798 ------
.../3.0/en-us/site/dev/contract/index.html | 752 -----
.../3.0/en-us/site/dev/contribution/index.html | 1104 --------
.../3.0/en-us/site/dev/design/index.html | 837 ------
.../3.0/en-us/site/dev/implementation/index.html | 832 ------
.../3.0/en-us/site/dev/impls/cache/index.html | 816 ------
.../3.0/en-us/site/dev/impls/cluster/index.html | 809 ------
.../3.0/en-us/site/dev/impls/compiler/index.html | 790 ------
.../en-us/site/dev/impls/config-center/index.html | 785 -----
.../3.0/en-us/site/dev/impls/container/index.html | 797 ------
.../3.0/en-us/site/dev/impls/dispatcher/index.html | 797 ------
.../3.0/en-us/site/dev/impls/exchanger/index.html | 822 ------
.../site/dev/impls/exporter-listener/index.html | 798 ------
.../site/dev/impls/extension-factory/index.html | 792 ------
.../3.0/en-us/site/dev/impls/filter/index.html | 824 ------
.../en-us/site/dev/impls/introduction/index.html | 710 -----
.../site/dev/impls/invoker-listener/index.html | 798 ------
.../en-us/site/dev/impls/load-balance/index.html | 798 ------
.../en-us/site/dev/impls/logger-adapter/index.html | 815 ------
.../3.0/en-us/site/dev/impls/merger/index.html | 794 ------
.../3.0/en-us/site/dev/impls/monitor/index.html | 808 ------
.../3.0/en-us/site/dev/impls/networker/index.html | 794 ------
.../3.0/en-us/site/dev/impls/page/index.html | 796 ------
.../3.0/en-us/site/dev/impls/protocol/index.html | 882 ------
.../en-us/site/dev/impls/proxy-factory/index.html | 800 ------
.../3.0/en-us/site/dev/impls/registry/index.html | 935 ------
.../3.0/en-us/site/dev/impls/remoting/index.html | 855 ------
.../3.0/en-us/site/dev/impls/router/index.html | 793 ------
.../3.0/en-us/site/dev/impls/serialize/index.html | 809 ------
.../en-us/site/dev/impls/status-checker/index.html | 799 ------
.../en-us/site/dev/impls/telnet-handler/index.html | 812 ------
.../3.0/en-us/site/dev/impls/threadpool/index.html | 795 ------
.../3.0/en-us/site/dev/impls/validation/index.html | 806 ------
documentations/3.0/en-us/site/dev/index.html | 715 -----
.../3.0/en-us/site/dev/introduction/index.html | 709 -----
.../site/dev/principals/code-detail/index.html | 729 -----
.../site/dev/principals/configuration/index.html | 761 -----
.../3.0/en-us/site/dev/principals/dummy/index.html | 890 ------
.../site/dev/principals/expansibility/index.html | 719 -----
.../en-us/site/dev/principals/extension/index.html | 799 ------
.../dev/principals/general-knowledge/index.html | 743 -----
.../site/dev/principals/introduction/index.html | 710 -----
.../site/dev/principals/robustness/index.html | 757 -----
.../3.0/en-us/site/dev/release/index.html | 773 -----
.../en-us/site/dev/sources/images/close-expand.jpg | Bin 19287 -> 0 bytes
.../dev/sources/images/configuration-override.png | Bin 11422 -> 0 bytes
.../3.0/en-us/site/dev/sources/images/ddd.jpg | Bin 19358 -> 0 bytes
.../en-us/site/dev/sources/images/design-step1.png | Bin 121672 -> 0 bytes
.../en-us/site/dev/sources/images/design-step2.png | Bin 141298 -> 0 bytes
.../en-us/site/dev/sources/images/design-step3.png | Bin 165828 -> 0 bytes
.../en-us/site/dev/sources/images/design-step4.png | Bin 240786 -> 0 bytes
.../en-us/site/dev/sources/images/dubbo-export.jpg | Bin 70132 -> 0 bytes
.../site/dev/sources/images/dubbo-extension.jpg | Bin 112692 -> 0 bytes
.../site/dev/sources/images/dubbo-framework.jpg | Bin 219759 -> 0 bytes
.../site/dev/sources/images/dubbo-modules.jpg | Bin 25411 -> 0 bytes
.../site/dev/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../en-us/site/dev/sources/images/dubbo-refer.jpg | Bin 105967 -> 0 bytes
.../site/dev/sources/images/dubbo-relation.jpg | Bin 30304 -> 0 bytes
.../dev/sources/images/dubbo_protocol_header.png | Bin 74833 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_export.jpg | Bin 47624 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_invoke.jpg | Bin 45874 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_refer.jpg | Bin 50211 -> 0 bytes
.../site/dev/sources/images/event-listener.jpg | Bin 13192 -> 0 bytes
.../en-us/site/dev/sources/images/filter-chain.jpg | Bin 41029 -> 0 bytes
.../en-us/site/dev/sources/images/mix-api-spi.jpg | Bin 17004 -> 0 bytes
.../en-us/site/dev/sources/images/open-expand.jpg | Bin 10549 -> 0 bytes
.../site/dev/sources/images/seperate-api-spi.jpg | Bin 23683 -> 0 bytes
.../apache-dubbo-page_dev/index.html | 743 -----
.../label-an-issue-guide_dev/index.html | 741 -----
.../new-committer-guide_dev/index.html | 785 -----
.../committer-guide/release-guide_dev/index.html | 1140 --------
.../committer-guide/website-guide_dev/index.html | 713 -----
.../become-a-committer_dev/index.html | 716 -----
.../cla-signing-guide_dev/index.html | 730 -----
.../dubbo-extension-guide_dev/index.html | 742 -----
.../mailing-list-subscription-guide_dev/index.html | 789 ------
.../new-contributor-guide_dev/index.html | 756 -----
.../reporting-security-issues_dev/index.html | 722 -----
.../software-donation-guide_dev/index.html | 808 ------
.../test-coverage-guide_dev/index.html | 729 -----
.../site/developers/developers_dev/index.html | 1041 -------
.../3.0/en-us/site/developers/guide_dev/index.html | 782 -----
.../site/developers/user-guide/faq_dev/index.html | 730 -----
.../3.0/en-us/site/fonts/fontawesome-webfont.eot | Bin 37405 -> 0 bytes
.../3.0/en-us/site/fonts/fontawesome-webfont.svg | 399 ---
.../3.0/en-us/site/fonts/fontawesome-webfont.ttf | Bin 79076 -> 0 bytes
.../3.0/en-us/site/fonts/fontawesome-webfont.woff | Bin 43572 -> 0 bytes
documentations/3.0/en-us/site/img/favicon.ico | Bin 1150 -> 0 bytes
documentations/3.0/en-us/site/index.html | 743 -----
.../3.0/en-us/site/js/jquery-2.1.1.min.js | 4 -
.../3.0/en-us/site/js/modernizr-2.8.3.min.js | 1 -
documentations/3.0/en-us/site/js/theme.js | 105 -
documentations/3.0/en-us/site/search.html | 708 -----
documentations/3.0/en-us/site/search/lunr.js | 2986 --------------------
documentations/3.0/en-us/site/search/main.js | 96 -
.../3.0/en-us/site/search/search_index.json | 1 -
documentations/3.0/en-us/site/search/worker.js | 128 -
documentations/3.0/en-us/site/sitemap.xml | 648 -----
documentations/3.0/en-us/site/sitemap.xml.gz | Bin 273 -> 0 bytes
documentations/3.0/en-us/site/user/LICENSE | 201 --
.../3.0/en-us/site/user/SUMMARY/index.html | 816 ------
.../3.0/en-us/site/user/benchmark-tool/index.html | 748 -----
.../3.0/en-us/site/user/best-practice/index.html | 783 -----
.../3.0/en-us/site/user/capacity-plan/index.html | 755 -----
.../site/user/configuration/annotation/index.html | 813 ------
.../en-us/site/user/configuration/api/index.html | 852 ------
.../configuration-load-process/index.html | 866 ------
.../3.0/en-us/site/user/configuration/index.html | 714 -----
.../site/user/configuration/properties/index.html | 744 -----
.../en-us/site/user/configuration/xml/index.html | 857 ------
.../3.0/en-us/site/user/coveragence/index.html | 724 -----
.../3.0/en-us/site/user/demos/accesslog/index.html | 792 ------
.../user/demos/async-call-deprecated/index.html | 761 -----
.../en-us/site/user/demos/async-call/index.html | 783 -----
.../demos/async-execute-on-provider/index.html | 778 -----
.../en-us/site/user/demos/attachment/index.html | 762 -----
.../site/user/demos/callback-parameter/index.html | 846 ------
.../site/user/demos/concurrency-control/index.html | 796 ------
.../site/user/demos/config-connections/index.html | 732 -----
.../user/demos/config-rule-deprecated/index.html | 744 -----
.../en-us/site/user/demos/config-rule/index.html | 771 -----
.../3.0/en-us/site/user/demos/context/index.html | 774 -----
.../en-us/site/user/demos/delay-publish/index.html | 784 -----
.../user/demos/distributed-transaction/index.html | 739 -----
.../3.0/en-us/site/user/demos/dump/index.html | 751 -----
.../en-us/site/user/demos/echo-service/index.html | 753 -----
.../en-us/site/user/demos/events-notify/index.html | 832 ------
.../site/user/demos/explicit-target/index.html | 768 -----
.../user/demos/fault-tolerent-strategy/index.html | 792 ------
.../site/user/demos/generic-reference/index.html | 826 ------
.../site/user/demos/generic-service/index.html | 779 -----
.../site/user/demos/graceful-shutdown/index.html | 765 -----
.../en-us/site/user/demos/group-merger/index.html | 779 -----
.../site/user/demos/hostname-binding/index.html | 823 ------
.../3.0/en-us/site/user/demos/index.html | 714 -----
.../en-us/site/user/demos/introduction/index.html | 712 -----
.../en-us/site/user/demos/lazy-connect/index.html | 741 -----
.../en-us/site/user/demos/loadbalance/index.html | 791 ------
.../en-us/site/user/demos/local-call/index.html | 773 -----
.../en-us/site/user/demos/local-mock/index.html | 811 ------
.../en-us/site/user/demos/local-stub/index.html | 771 -----
.../site/user/demos/logger-strategy/index.html | 755 -----
.../site/user/demos/multi-protocols/index.html | 781 -----
.../site/user/demos/multi-registry/index.html | 814 ------
.../site/user/demos/multi-versions/index.html | 764 -----
.../3.0/en-us/site/user/demos/netty4/index.html | 761 -----
.../user/demos/parameter-validation/index.html | 910 ------
.../site/user/demos/preflight-check/index.html | 780 -----
.../user/demos/reference-config-cache/index.html | 734 -----
.../en-us/site/user/demos/registry-only/index.html | 748 -----
.../en-us/site/user/demos/result-cache/index.html | 763 -----
.../en-us/site/user/demos/routing-rule/index.html | 899 ------
.../en-us/site/user/demos/serialization/index.html | 804 ------
.../site/user/demos/service-container/index.html | 792 ------
.../site/user/demos/service-downgrade/index.html | 752 -----
.../en-us/site/user/demos/service-group/index.html | 760 -----
.../site/user/demos/static-service/index.html | 754 -----
.../en-us/site/user/demos/stickiness/index.html | 746 -----
.../site/user/demos/subscribe-only/index.html | 746 -----
.../en-us/site/user/demos/thread-model/index.html | 771 -----
.../site/user/demos/token-authorization/index.html | 767 -----
.../3.0/en-us/site/user/dependencies/index.html | 794 ------
documentations/3.0/en-us/site/user/index.html | 715 -----
.../user/languages/erlang/reference/index.html | 722 -----
.../user/languages/erlang/serialization/index.html | 736 -----
.../site/user/languages/erlang/service/index.html | 752 -----
.../site/user/languages/erlang/start/index.html | 757 -----
.../3.0/en-us/site/user/maturity/index.html | 1344 ---------
.../3.0/en-us/site/user/perf-test/index.html | 1080 -------
.../site/user/preface/architecture/index.html | 857 ------
.../en-us/site/user/preface/background/index.html | 758 -----
.../3.0/en-us/site/user/preface/index.html | 714 -----
.../site/user/preface/requirements/index.html | 715 -----
.../3.0/en-us/site/user/preface/usage/index.html | 773 -----
.../3.0/en-us/site/user/quick-start/index.html | 947 -------
.../3.0/en-us/site/user/recommend/index.html | 882 ------
.../3.0/en-us/site/user/references/api/index.html | 753 -----
.../en-us/site/user/references/maven/index.html | 751 -----
.../references/metadata/introduction/index.html | 1019 -------
.../site/user/references/protocol/dubbo/index.html | 850 ------
.../user/references/protocol/hessian/index.html | 798 ------
.../site/user/references/protocol/http/index.html | 791 ------
.../references/protocol/introduction/index.html | 710 -----
.../user/references/protocol/memcached/index.html | 733 -----
.../site/user/references/protocol/redis/index.html | 733 -----
.../site/user/references/protocol/rest/index.html | 1311 ---------
.../site/user/references/protocol/rmi/index.html | 811 ------
.../user/references/protocol/thrift/index.html | 768 -----
.../user/references/protocol/webservice/index.html | 793 ------
.../3.0/en-us/site/user/references/qos/index.html | 911 ------
.../references/registry/introduction/index.html | 710 -----
.../user/references/registry/multicast/index.html | 768 -----
.../site/user/references/registry/nacos/index.html | 790 ------
.../site/user/references/registry/redis/index.html | 805 ------
.../user/references/registry/simple/index.html | 780 -----
.../user/references/registry/zookeeper/index.html | 851 ------
.../en-us/site/user/references/telnet/index.html | 829 ------
.../references/xml/dubbo-application/index.html | 833 ------
.../user/references/xml/dubbo-argument/index.html | 788 ------
.../references/xml/dubbo-config-center/index.html | 869 ------
.../user/references/xml/dubbo-consumer/index.html | 933 ------
.../user/references/xml/dubbo-method/index.html | 918 ------
.../user/references/xml/dubbo-module/index.html | 793 ------
.../user/references/xml/dubbo-monitor/index.html | 773 -----
.../user/references/xml/dubbo-parameter/index.html | 782 -----
.../user/references/xml/dubbo-protocol/index.html | 993 -------
.../user/references/xml/dubbo-provider/index.html | 1193 --------
.../user/references/xml/dubbo-reference/index.html | 1023 -------
.../user/references/xml/dubbo-registry/index.html | 933 ------
.../user/references/xml/dubbo-service/index.html | 1063 -------
.../user/references/xml/introduction/index.html | 720 -----
documentations/3.0/en-us/site/user/rest/index.html | 1724 -----------
.../3.0/en-us/site/user/simple-monitor/index.html | 773 -----
.../3.0/en-us/site/user/sources/images/1kres.png | Bin 39384 -> 0 bytes
.../3.0/en-us/site/user/sources/images/1ktps.png | Bin 38814 -> 0 bytes
.../3.0/en-us/site/user/sources/images/200kres.png | Bin 39229 -> 0 bytes
.../3.0/en-us/site/user/sources/images/200ktps.png | Bin 38997 -> 0 bytes
.../3.0/en-us/site/user/sources/images/50kres.png | Bin 39733 -> 0 bytes
.../3.0/en-us/site/user/sources/images/50ktps.png | Bin 39723 -> 0 bytes
.../3.0/en-us/site/user/sources/images/arch.png | Bin 15546 -> 0 bytes
.../3.0/en-us/site/user/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../site/user/sources/images/code-coverage.jpg | Bin 141776 -> 0 bytes
.../site/user/sources/images/code-dependency.jpg | Bin 138868 -> 0 bytes
.../site/user/sources/images/code-quality1.jpg | Bin 56913 -> 0 bytes
.../site/user/sources/images/code-quality2.jpg | Bin 56913 -> 0 bytes
.../site/user/sources/images/code-quality3.jpg | Bin 56913 -> 0 bytes
.../site/user/sources/images/code-quality4.jpg | Bin 56913 -> 0 bytes
.../site/user/sources/images/code-quality5.jpg | Bin 41672 -> 0 bytes
.../site/user/sources/images/code-quality6.jpg | Bin 41672 -> 0 bytes
.../site/user/sources/images/code-quality7.jpg | Bin 41672 -> 0 bytes
.../site/user/sources/images/code-tendency.jpg | Bin 54729 -> 0 bytes
.../3.0/en-us/site/user/sources/images/context.png | Bin 46114 -> 0 bytes
.../sources/images/dubbo-architecture-future.jpg | Bin 55605 -> 0 bytes
.../sources/images/dubbo-architecture-roadmap.jpg | Bin 33931 -> 0 bytes
.../user/sources/images/dubbo-architecture.jpg | Bin 18810 -> 0 bytes
.../user/sources/images/dubbo-config-override.jpg | Bin 68132 -> 0 bytes
.../site/user/sources/images/dubbo-config.jpg | Bin 69630 -> 0 bytes
.../site/user/sources/images/dubbo-directly.jpg | Bin 38922 -> 0 bytes
.../sources/images/dubbo-properties-override.jpg | Bin 24590 -> 0 bytes
.../site/user/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../user/sources/images/dubbo-redis-registry.jpg | Bin 47205 -> 0 bytes
.../sources/images/dubbo-service-governance.jpg | Bin 67000 -> 0 bytes
.../en-us/site/user/sources/images/dubbo-token.jpg | Bin 17153 -> 0 bytes
.../3.0/en-us/site/user/sources/images/future.jpg | Bin 20793 -> 0 bytes
.../3.0/en-us/site/user/sources/images/jta-xa.jpg | Bin 37931 -> 0 bytes
.../site/user/sources/images/lock-get-bean.jpg | Bin 109801 -> 0 bytes
.../site/user/sources/images/lock-init-context.jpg | Bin 39227 -> 0 bytes
.../en-us/site/user/sources/images/multicast.jpg | Bin 20269 -> 0 bytes
.../3.0/en-us/site/user/sources/images/pojores.png | Bin 37733 -> 0 bytes
.../3.0/en-us/site/user/sources/images/pojotps.png | Bin 39797 -> 0 bytes
.../3.0/en-us/site/user/sources/images/stub.jpg | Bin 28646 -> 0 bytes
.../site/user/sources/images/subscribe-only.jpg | Bin 20626 -> 0 bytes
...pg-version=1&modificationDate=1326468174000.jpg | Bin 20626 -> 0 bytes
.../en-us/site/user/sources/images/zookeeper.jpg | Bin 31272 -> 0 bytes
documentations/3.0/zh-cn/docs/admin/LICENSE | 201 --
documentations/3.0/zh-cn/docs/admin/README.md | 1 -
documentations/3.0/zh-cn/docs/admin/SUMMARY.md | 4 -
.../3.0/zh-cn/docs/admin/install/admin-console.md | 40 -
.../3.0/zh-cn/docs/admin/install/consumer-demo.md | 21 -
.../3.0/zh-cn/docs/admin/install/introduction.md | 13 -
.../3.0/zh-cn/docs/admin/install/provider-demo.md | 19 -
.../3.0/zh-cn/docs/admin/install/redis.md | 54 -
.../docs/admin/install/simple-monitor-center.md | 3 -
.../docs/admin/install/simple-registry-center.md | 2 -
.../3.0/zh-cn/docs/admin/install/zookeeper.md | 98 -
.../3.0/zh-cn/docs/admin/introduction.md | 65 -
.../3.0/zh-cn/docs/admin/ops/dubbo-ops.md | 25 -
.../3.0/zh-cn/docs/admin/ops/introduction.md | 1 -
.../3.0/zh-cn/docs/admin/ops/pinpoint.md | 415 ---
.../3.0/zh-cn/docs/admin/ops/skywalking.md | 133 -
.../3.0/zh-cn/docs/admin/serviceGovernance.md | 42 -
.../3.0/zh-cn/docs/admin/serviceSearch.md | 7 -
documentations/3.0/zh-cn/docs/admin/serviceTest.md | 1 -
.../zh-cn/docs/admin/sources/images/blackList.jpg | Bin 99079 -> 0 bytes
.../3.0/zh-cn/docs/admin/sources/images/config.jpg | Bin 137909 -> 0 bytes
.../3.0/zh-cn/docs/admin/sources/images/detail.jpg | Bin 188392 -> 0 bytes
.../docs/admin/sources/images/dubbo-add-config.jpg | Bin 303596 -> 0 bytes
.../docs/admin/sources/images/dubbo-add-route.jpg | Bin 330146 -> 0 bytes
.../admin/sources/images/dubbo-applications.png | Bin 93036 -> 0 bytes
.../docs/admin/sources/images/dubbo-consumers.jpg | Bin 274307 -> 0 bytes
.../admin/sources/images/dubbo-monitor-simple.jpg | Bin 87670 -> 0 bytes
.../docs/admin/sources/images/dubbo-providers.jpg | Bin 272674 -> 0 bytes
.../docs/admin/sources/images/dubbo-search.jpg | Bin 224751 -> 0 bytes
.../admin/sources/images/pinpoint-calltree.png | Bin 693731 -> 0 bytes
.../docs/admin/sources/images/pinpoint-home.png | Bin 317984 -> 0 bytes
.../admin/sources/images/pinpoint-mixedview.png | Bin 480963 -> 0 bytes
.../docs/admin/sources/images/searchResult.png | Bin 168461 -> 0 bytes
.../docs/admin/sources/images/skywalking-alarm.png | Bin 181739 -> 0 bytes
.../sources/images/skywalking-application.png | Bin 229539 -> 0 bytes
.../images/skywalking-application_instance.png | Bin 203651 -> 0 bytes
.../admin/sources/images/skywalking-dashboard.png | Bin 257273 -> 0 bytes
.../sources/images/skywalking-service-consumer.png | Bin 282541 -> 0 bytes
.../sources/images/skywalking-service-provider.png | Bin 366038 -> 0 bytes
.../admin/sources/images/skywalking-span-Info.png | Bin 192403 -> 0 bytes
.../admin/sources/images/skywalking-topology.png | Bin 173667 -> 0 bytes
.../docs/admin/sources/images/skywalking-trace.png | Bin 217096 -> 0 bytes
.../3.0/zh-cn/docs/admin/sources/images/weight.jpg | Bin 89265 -> 0 bytes
documentations/3.0/zh-cn/docs/dev/LICENSE | 201 --
documentations/3.0/zh-cn/docs/dev/README.md | 1 -
documentations/3.0/zh-cn/docs/dev/SPI.md | 237 --
documentations/3.0/zh-cn/docs/dev/SUMMARY.md | 50 -
documentations/3.0/zh-cn/docs/dev/TCK.md | 19 -
documentations/3.0/zh-cn/docs/dev/build.md | 80 -
documentations/3.0/zh-cn/docs/dev/checklist.md | 27 -
documentations/3.0/zh-cn/docs/dev/code-smell.md | 205 --
documentations/3.0/zh-cn/docs/dev/coding.md | 53 -
documentations/3.0/zh-cn/docs/dev/contract.md | 14 -
documentations/3.0/zh-cn/docs/dev/contribution.md | 45 -
documentations/3.0/zh-cn/docs/dev/design.md | 99 -
.../3.0/zh-cn/docs/dev/implementation.md | 226 --
documentations/3.0/zh-cn/docs/dev/impls/cache.md | 83 -
documentations/3.0/zh-cn/docs/dev/impls/cluster.md | 74 -
.../3.0/zh-cn/docs/dev/impls/compiler.md | 55 -
.../3.0/zh-cn/docs/dev/impls/config-center.md | 97 -
.../3.0/zh-cn/docs/dev/impls/container.md | 62 -
.../3.0/zh-cn/docs/dev/impls/dispatcher.md | 62 -
.../3.0/zh-cn/docs/dev/impls/exchanger.md | 90 -
.../3.0/zh-cn/docs/dev/impls/exporter-listener.md | 66 -
.../3.0/zh-cn/docs/dev/impls/extension-factory.md | 57 -
documentations/3.0/zh-cn/docs/dev/impls/filter.md | 89 -
.../3.0/zh-cn/docs/dev/impls/introduction.md | 3 -
.../3.0/zh-cn/docs/dev/impls/invoker-listener.md | 64 -
.../3.0/zh-cn/docs/dev/impls/load-balance.md | 63 -
.../3.0/zh-cn/docs/dev/impls/logger-adapter.md | 84 -
documentations/3.0/zh-cn/docs/dev/impls/merger.md | 60 -
documentations/3.0/zh-cn/docs/dev/impls/monitor.md | 75 -
.../3.0/zh-cn/docs/dev/impls/networker.md | 59 -
documentations/3.0/zh-cn/docs/dev/impls/page.md | 61 -
.../3.0/zh-cn/docs/dev/impls/protocol.md | 151 -
.../3.0/zh-cn/docs/dev/impls/proxy-factory.md | 65 -
.../3.0/zh-cn/docs/dev/impls/registry.md | 205 --
.../3.0/zh-cn/docs/dev/impls/remoting.md | 122 -
documentations/3.0/zh-cn/docs/dev/impls/router.md | 58 -
.../3.0/zh-cn/docs/dev/impls/serialize.md | 72 -
.../3.0/zh-cn/docs/dev/impls/status-checker.md | 64 -
.../3.0/zh-cn/docs/dev/impls/telnet-handler.md | 77 -
.../3.0/zh-cn/docs/dev/impls/threadpool.md | 61 -
.../3.0/zh-cn/docs/dev/impls/validation.md | 75 -
documentations/3.0/zh-cn/docs/dev/introduction.md | 1 -
.../3.0/zh-cn/docs/dev/principals/code-detail.md | 35 -
.../3.0/zh-cn/docs/dev/principals/configuration.md | 97 -
.../3.0/zh-cn/docs/dev/principals/dummy.md | 204 --
.../3.0/zh-cn/docs/dev/principals/expansibility.md | 18 -
.../3.0/zh-cn/docs/dev/principals/extension.md | 136 -
.../zh-cn/docs/dev/principals/general-knowledge.md | 69 -
.../3.0/zh-cn/docs/dev/principals/introduction.md | 3 -
.../3.0/zh-cn/docs/dev/principals/robustness.md | 84 -
documentations/3.0/zh-cn/docs/dev/release.md | 34 -
.../zh-cn/docs/dev/sources/images/close-expand.jpg | Bin 19287 -> 0 bytes
.../dev/sources/images/configuration-override.png | Bin 11422 -> 0 bytes
.../3.0/zh-cn/docs/dev/sources/images/ddd.jpg | Bin 19358 -> 0 bytes
.../zh-cn/docs/dev/sources/images/design-step1.png | Bin 121672 -> 0 bytes
.../zh-cn/docs/dev/sources/images/design-step2.png | Bin 141298 -> 0 bytes
.../zh-cn/docs/dev/sources/images/design-step3.png | Bin 165828 -> 0 bytes
.../zh-cn/docs/dev/sources/images/design-step4.png | Bin 240786 -> 0 bytes
.../zh-cn/docs/dev/sources/images/dubbo-export.jpg | Bin 70132 -> 0 bytes
.../docs/dev/sources/images/dubbo-extension.jpg | Bin 112692 -> 0 bytes
.../docs/dev/sources/images/dubbo-framework.jpg | Bin 219759 -> 0 bytes
.../docs/dev/sources/images/dubbo-modules.jpg | Bin 25411 -> 0 bytes
.../docs/dev/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../zh-cn/docs/dev/sources/images/dubbo-refer.jpg | Bin 105967 -> 0 bytes
.../docs/dev/sources/images/dubbo-relation.jpg | Bin 30304 -> 0 bytes
.../dev/sources/images/dubbo_protocol_header.png | Bin 74833 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_export.jpg | Bin 47624 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_invoke.jpg | Bin 45874 -> 0 bytes
.../docs/dev/sources/images/dubbo_rpc_refer.jpg | Bin 50211 -> 0 bytes
.../docs/dev/sources/images/event-listener.jpg | Bin 13192 -> 0 bytes
.../zh-cn/docs/dev/sources/images/filter-chain.jpg | Bin 41029 -> 0 bytes
.../zh-cn/docs/dev/sources/images/mix-api-spi.jpg | Bin 17004 -> 0 bytes
.../zh-cn/docs/dev/sources/images/open-expand.jpg | Bin 10549 -> 0 bytes
.../docs/dev/sources/images/seperate-api-spi.jpg | Bin 23683 -> 0 bytes
.../committer-guide/apache-dubbo-page_dev.md | 28 -
.../committer-guide/label-an-issue-guide_dev.md | 27 -
.../committer-guide/new-committer-guide_dev.md | 73 -
.../committer-guide/release-guide_dev.md | 477 ----
.../committer-guide/website-guide_dev.md | 5 -
.../contributor-guide/become-a-committer_dev.md | 15 -
.../contributor-guide/cla-signing-guide_dev.md | 24 -
.../contributor-guide/dubbo-extension-guide_dev.md | 47 -
.../mailing-list-subscription-guide_dev.md | 80 -
.../contributor-guide/new-contributor-guide_dev.md | 38 -
.../reporting-security-issues_dev.md | 21 -
.../software-donation-guide_dev.md | 112 -
.../contributor-guide/test-coverage-guide_dev.md | 16 -
.../3.0/zh-cn/docs/developers/developers_dev.md | 58 -
.../3.0/zh-cn/docs/developers/guide_dev.md | 82 -
.../zh-cn/docs/developers/user-guide/faq_dev.md | 25 -
documentations/3.0/zh-cn/docs/index.md | 25 -
.../docs/source_code_guide/adaptive-extension.md | 788 ------
.../3.0/zh-cn/docs/source_code_guide/cluster.md | 606 ----
.../3.0/zh-cn/docs/source_code_guide/directory.md | 542 ----
.../3.0/zh-cn/docs/source_code_guide/dubbo-spi.md | 432 ---
.../zh-cn/docs/source_code_guide/export-service.md | 1518 ----------
.../zh-cn/docs/source_code_guide/loadbalance.md | 767 -----
.../zh-cn/docs/source_code_guide/refer-service.md | 899 ------
.../3.0/zh-cn/docs/source_code_guide/router.md | 468 ---
.../source_code_guide/service-invoking-process.md | 1974 -------------
.../source_code_guide/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../images/consistent-hash-data-incline.jpg | Bin 101943 -> 0 bytes
.../sources/images/consistent-hash-invoker.jpg | Bin 87844 -> 0 bytes
.../sources/images/consistent-hash.jpg | Bin 95740 -> 0 bytes
.../sources/images/data-format.jpg | Bin 115165 -> 0 bytes
.../sources/images/directory-inherit-hierarchy.png | Bin 69024 -> 0 bytes
.../sources/images/dispatcher-location.jpg | Bin 89871 -> 0 bytes
.../sources/images/dubbo-spi-result.jpg | Bin 33007 -> 0 bytes
.../sources/images/java-spi-result.jpg | Bin 46805 -> 0 bytes
.../sources/images/request-id-application.jpg | Bin 217379 -> 0 bytes
.../sources/images/send-request-process.jpg | Bin 83592 -> 0 bytes
.../sources/images/send-request-thread-stack.jpg | Bin 213679 -> 0 bytes
.../sources/images/service-registry.png | Bin 57116 -> 0 bytes
documentations/3.0/zh-cn/docs/user/LICENSE | 201 --
documentations/3.0/zh-cn/docs/user/README.md | 3 -
documentations/3.0/zh-cn/docs/user/SUMMARY.md | 110 -
.../3.0/zh-cn/docs/user/benchmark-tool.md | 28 -
.../3.0/zh-cn/docs/user/best-practice.md | 69 -
.../3.0/zh-cn/docs/user/capacity-plan.md | 23 -
.../zh-cn/docs/user/configuration/annotation.md | 95 -
.../3.0/zh-cn/docs/user/configuration/api.md | 121 -
.../zh-cn/docs/user/configuration/config-center.md | 150 -
.../configuration/configuration-load-process.md | 181 --
.../user/configuration/environment-variables.md | 31 -
.../3.0/zh-cn/docs/user/configuration/index.md | 1 -
.../user/configuration/properties-deprecated.md | 42 -
.../zh-cn/docs/user/configuration/properties.md | 37 -
.../3.0/zh-cn/docs/user/configuration/xml.md | 91 -
documentations/3.0/zh-cn/docs/user/coveragence.md | 16 -
.../docs/user/demos/GooglePb-generic-reference.md | 80 -
.../3.0/zh-cn/docs/user/demos/accesslog.md | 15 -
.../zh-cn/docs/user/demos/async-call-deprecated.md | 57 -
.../3.0/zh-cn/docs/user/demos/async-call.md | 134 -
.../docs/user/demos/async-execute-on-provider.md | 95 -
.../3.0/zh-cn/docs/user/demos/attachment.md | 30 -
documentations/3.0/zh-cn/docs/user/demos/auth.md | 28 -
.../zh-cn/docs/user/demos/callback-parameter.md | 112 -
.../zh-cn/docs/user/demos/concurrency-control.md | 68 -
.../zh-cn/docs/user/demos/config-connections.md | 35 -
.../docs/user/demos/config-rule-deprecated.md | 48 -
.../3.0/zh-cn/docs/user/demos/config-rule.md | 181 --
.../zh-cn/docs/user/demos/consumer-threadpool.md | 41 -
.../3.0/zh-cn/docs/user/demos/context.md | 40 -
.../3.0/zh-cn/docs/user/demos/delay-publish.md | 53 -
.../docs/user/demos/distributed-transaction.md | 9 -
documentations/3.0/zh-cn/docs/user/demos/dump.md | 18 -
.../3.0/zh-cn/docs/user/demos/echo-service.md | 25 -
.../3.0/zh-cn/docs/user/demos/events-notify.md | 97 -
.../3.0/zh-cn/docs/user/demos/explicit-target.md | 41 -
.../docs/user/demos/fault-tolerent-strategy.md | 78 -
.../3.0/zh-cn/docs/user/demos/generic-reference.md | 97 -
.../3.0/zh-cn/docs/user/demos/generic-service.md | 45 -
.../3.0/zh-cn/docs/user/demos/graceful-shutdown.md | 30 -
.../3.0/zh-cn/docs/user/demos/group-merger.md | 54 -
.../3.0/zh-cn/docs/user/demos/hostname-binding.md | 58 -
documentations/3.0/zh-cn/docs/user/demos/index.md | 1 -
.../3.0/zh-cn/docs/user/demos/introduction.md | 2 -
.../3.0/zh-cn/docs/user/demos/lazy-connect.md | 9 -
.../3.0/zh-cn/docs/user/demos/loadbalance.md | 60 -
.../3.0/zh-cn/docs/user/demos/local-call.md | 46 -
.../3.0/zh-cn/docs/user/demos/local-mock.md | 100 -
.../3.0/zh-cn/docs/user/demos/local-stub.md | 44 -
.../3.0/zh-cn/docs/user/demos/logger-strategy.md | 23 -
.../3.0/zh-cn/docs/user/demos/multi-protocols.md | 47 -
.../3.0/zh-cn/docs/user/demos/multi-registry.md | 84 -
.../3.0/zh-cn/docs/user/demos/multi-versions.md | 41 -
documentations/3.0/zh-cn/docs/user/demos/netty4.md | 35 -
.../zh-cn/docs/user/demos/parameter-validation.md | 183 --
.../3.0/zh-cn/docs/user/demos/preflight-check.md | 55 -
.../3.0/zh-cn/docs/user/demos/protobuf-idl.md | 31 -
.../docs/user/demos/reference-config-cache.md | 37 -
.../3.0/zh-cn/docs/user/demos/registry-only.md | 17 -
.../3.0/zh-cn/docs/user/demos/result-cache.md | 28 -
.../docs/user/demos/routing-rule-deprecated.md | 193 --
.../3.0/zh-cn/docs/user/demos/routing-rule.md | 250 --
.../3.0/zh-cn/docs/user/demos/serialization.md | 80 -
.../3.0/zh-cn/docs/user/demos/service-container.md | 61 -
.../3.0/zh-cn/docs/user/demos/service-downgrade.md | 18 -
.../3.0/zh-cn/docs/user/demos/service-group.md | 25 -
.../3.0/zh-cn/docs/user/demos/set-host.md | 59 -
.../docs/user/demos/simplify-registry-data.md | 232 --
.../3.0/zh-cn/docs/user/demos/static-service.md | 25 -
.../3.0/zh-cn/docs/user/demos/stickiness.md | 18 -
.../3.0/zh-cn/docs/user/demos/subscribe-only.md | 19 -
.../3.0/zh-cn/docs/user/demos/thread-model.md | 31 -
documentations/3.0/zh-cn/docs/user/demos/tls.md | 44 -
.../zh-cn/docs/user/demos/token-authorization.md | 31 -
documentations/3.0/zh-cn/docs/user/dependencies.md | 64 -
.../zh-cn/docs/user/languages/erlang/reference.md | 15 -
.../docs/user/languages/erlang/serialization.md | 21 -
.../zh-cn/docs/user/languages/erlang/service.md | 22 -
.../3.0/zh-cn/docs/user/languages/erlang/start.md | 60 -
documentations/3.0/zh-cn/docs/user/maturity.md | 100 -
.../zh-cn/docs/user/new-features-in-a-glance.md | 48 -
documentations/3.0/zh-cn/docs/user/perf-test.md | 172 --
.../3.0/zh-cn/docs/user/preface/architecture.md | 66 -
.../3.0/zh-cn/docs/user/preface/background.md | 25 -
.../3.0/zh-cn/docs/user/preface/index.md | 1 -
.../3.0/zh-cn/docs/user/preface/requirements.md | 19 -
.../3.0/zh-cn/docs/user/preface/usage.md | 39 -
documentations/3.0/zh-cn/docs/user/quick-start.md | 138 -
documentations/3.0/zh-cn/docs/user/recommend.md | 171 --
.../3.0/zh-cn/docs/user/references/api.md | 62 -
.../3.0/zh-cn/docs/user/references/maven.md | 19 -
.../docs/user/references/metadata/introduction.md | 368 ---
.../user/references/metadata/metadata-redis.md | 1 -
.../user/references/metadata/metadata-zookeeper.md | 1 -
.../zh-cn/docs/user/references/protocol/dubbo.md | 123 -
.../zh-cn/docs/user/references/protocol/gRPC.md | 19 -
.../zh-cn/docs/user/references/protocol/hessian.md | 68 -
.../zh-cn/docs/user/references/protocol/http.md | 57 -
.../docs/user/references/protocol/introduction.md | 3 -
.../docs/user/references/protocol/memcached.md | 44 -
.../zh-cn/docs/user/references/protocol/redis.md | 44 -
.../zh-cn/docs/user/references/protocol/rest.md | 741 -----
.../3.0/zh-cn/docs/user/references/protocol/rmi.md | 85 -
.../zh-cn/docs/user/references/protocol/thrift.md | 35 -
.../docs/user/references/protocol/webservice.md | 110 -
.../3.0/zh-cn/docs/user/references/qos.md | 241 --
.../docs/user/references/registry/introduction.md | 3 -
.../docs/user/references/registry/multicast.md | 38 -
.../zh-cn/docs/user/references/registry/nacos.md | 130 -
.../zh-cn/docs/user/references/registry/redis.md | 76 -
.../zh-cn/docs/user/references/registry/simple.md | 49 -
.../docs/user/references/registry/zookeeper.md | 151 -
.../3.0/zh-cn/docs/user/references/telnet.md | 105 -
.../docs/user/references/xml/dubbo-application.md | 14 -
.../docs/user/references/xml/dubbo-argument.md | 14 -
.../user/references/xml/dubbo-config-center.md | 19 -
.../docs/user/references/xml/dubbo-consumer.md | 24 -
.../zh-cn/docs/user/references/xml/dubbo-method.md | 30 -
.../zh-cn/docs/user/references/xml/dubbo-module.md | 10 -
.../docs/user/references/xml/dubbo-monitor.md | 8 -
.../docs/user/references/xml/dubbo-parameter.md | 22 -
.../docs/user/references/xml/dubbo-protocol.md | 30 -
.../docs/user/references/xml/dubbo-provider.md | 50 -
.../docs/user/references/xml/dubbo-reference.md | 33 -
.../docs/user/references/xml/dubbo-registry.md | 30 -
.../docs/user/references/xml/dubbo-service.md | 37 -
.../zh-cn/docs/user/references/xml/introduction.md | 15 -
documentations/3.0/zh-cn/docs/user/rest.md | 1216 --------
.../3.0/zh-cn/docs/user/serialization.md | 225 --
.../3.0/zh-cn/docs/user/simple-monitor.md | 84 -
.../3.0/zh-cn/docs/user/sources/images/1kres.png | Bin 39384 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/1ktps.png | Bin 38814 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/200kres.png | Bin 39229 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/200ktps.png | Bin 38997 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/50kres.png | Bin 39733 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/50ktps.png | Bin 39723 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/arch.png | Bin 15546 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../docs/user/sources/images/code-coverage.jpg | Bin 141776 -> 0 bytes
.../docs/user/sources/images/code-dependency.jpg | Bin 138868 -> 0 bytes
.../docs/user/sources/images/code-quality1.jpg | Bin 56913 -> 0 bytes
.../docs/user/sources/images/code-quality5.jpg | Bin 41672 -> 0 bytes
.../docs/user/sources/images/code-tendency.jpg | Bin 54729 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/context.png | Bin 46114 -> 0 bytes
.../sources/images/dubbo-architecture-future.jpg | Bin 55605 -> 0 bytes
.../sources/images/dubbo-architecture-roadmap.jpg | Bin 33931 -> 0 bytes
.../user/sources/images/dubbo-architecture.jpg | Bin 18810 -> 0 bytes
.../user/sources/images/dubbo-config-override.jpg | Bin 68132 -> 0 bytes
.../docs/user/sources/images/dubbo-config.jpg | Bin 69630 -> 0 bytes
.../docs/user/sources/images/dubbo-directly.jpg | Bin 38922 -> 0 bytes
.../sources/images/dubbo-properties-override.jpg | Bin 24590 -> 0 bytes
.../docs/user/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../user/sources/images/dubbo-redis-registry.jpg | Bin 47205 -> 0 bytes
.../sources/images/dubbo-service-governance.jpg | Bin 67000 -> 0 bytes
.../zh-cn/docs/user/sources/images/dubbo-token.jpg | Bin 17153 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/future.jpg | Bin 20793 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/jta-xa.jpg | Bin 37931 -> 0 bytes
.../docs/user/sources/images/lock-get-bean.jpg | Bin 109801 -> 0 bytes
.../docs/user/sources/images/lock-init-context.jpg | Bin 39227 -> 0 bytes
.../zh-cn/docs/user/sources/images/multicast.jpg | Bin 20269 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/pojores.png | Bin 37733 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/pojotps.png | Bin 39797 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/rest.jpg | Bin 206610 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/rt.png | Bin 31098 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/stub.jpg | Bin 28646 -> 0 bytes
.../docs/user/sources/images/subscribe-only.jpg | Bin 20626 -> 0 bytes
...pg-version=1&modificationDate=1326468174000.jpg | Bin 20626 -> 0 bytes
.../3.0/zh-cn/docs/user/sources/images/tps.png | Bin 33114 -> 0 bytes
.../zh-cn/docs/user/sources/images/zookeeper.jpg | Bin 31272 -> 0 bytes
.../3.0/zh-cn/docs/user/versions/index.md | 3 -
.../3.0/zh-cn/docs/user/versions/version-270.md | 286 --
documentations/3.0/zh-cn/mkdocs.yml | 172 --
documentations/3.0/zh-cn/site/404.html | 769 -----
documentations/3.0/zh-cn/site/admin/LICENSE | 201 --
.../3.0/zh-cn/site/admin/SUMMARY/index.html | 784 -----
documentations/3.0/zh-cn/site/admin/index.html | 782 -----
.../site/admin/install/admin-console/index.html | 802 ------
.../site/admin/install/consumer-demo/index.html | 790 ------
.../site/admin/install/introduction/index.html | 783 -----
.../site/admin/install/provider-demo/index.html | 789 ------
.../3.0/zh-cn/site/admin/install/redis/index.html | 814 ------
.../admin/install/simple-monitor-center/index.html | 778 -----
.../install/simple-registry-center/index.html | 777 -----
.../zh-cn/site/admin/install/zookeeper/index.html | 846 ------
.../3.0/zh-cn/site/admin/introduction/index.html | 871 ------
.../3.0/zh-cn/site/admin/ops/dubbo-ops/index.html | 789 ------
.../zh-cn/site/admin/ops/introduction/index.html | 777 -----
.../3.0/zh-cn/site/admin/ops/pinpoint/index.html | 1168 --------
.../3.0/zh-cn/site/admin/ops/skywalking/index.html | 888 ------
.../zh-cn/site/admin/serviceGovernance/index.html | 841 ------
.../3.0/zh-cn/site/admin/serviceSearch/index.html | 804 ------
.../3.0/zh-cn/site/admin/serviceTest/index.html | 793 ------
.../zh-cn/site/admin/sources/images/blackList.jpg | Bin 99079 -> 0 bytes
.../3.0/zh-cn/site/admin/sources/images/config.jpg | Bin 137909 -> 0 bytes
.../3.0/zh-cn/site/admin/sources/images/detail.jpg | Bin 188392 -> 0 bytes
.../site/admin/sources/images/dubbo-add-config.jpg | Bin 303596 -> 0 bytes
.../site/admin/sources/images/dubbo-add-route.jpg | Bin 330146 -> 0 bytes
.../admin/sources/images/dubbo-applications.png | Bin 93036 -> 0 bytes
.../site/admin/sources/images/dubbo-consumers.jpg | Bin 274307 -> 0 bytes
.../admin/sources/images/dubbo-monitor-simple.jpg | Bin 87670 -> 0 bytes
.../site/admin/sources/images/dubbo-providers.jpg | Bin 272674 -> 0 bytes
.../site/admin/sources/images/dubbo-search.jpg | Bin 224751 -> 0 bytes
.../admin/sources/images/pinpoint-calltree.png | Bin 693731 -> 0 bytes
.../site/admin/sources/images/pinpoint-home.png | Bin 317984 -> 0 bytes
.../admin/sources/images/pinpoint-mixedview.png | Bin 480963 -> 0 bytes
.../site/admin/sources/images/searchResult.png | Bin 168461 -> 0 bytes
.../site/admin/sources/images/skywalking-alarm.png | Bin 181739 -> 0 bytes
.../sources/images/skywalking-application.png | Bin 229539 -> 0 bytes
.../images/skywalking-application_instance.png | Bin 203651 -> 0 bytes
.../admin/sources/images/skywalking-dashboard.png | Bin 257273 -> 0 bytes
.../sources/images/skywalking-service-consumer.png | Bin 282541 -> 0 bytes
.../sources/images/skywalking-service-provider.png | Bin 366038 -> 0 bytes
.../admin/sources/images/skywalking-span-Info.png | Bin 192403 -> 0 bytes
.../admin/sources/images/skywalking-topology.png | Bin 173667 -> 0 bytes
.../site/admin/sources/images/skywalking-trace.png | Bin 217096 -> 0 bytes
.../3.0/zh-cn/site/admin/sources/images/weight.jpg | Bin 89265 -> 0 bytes
documentations/3.0/zh-cn/site/css/theme.css | 12 -
documentations/3.0/zh-cn/site/css/theme_extra.css | 197 --
documentations/3.0/zh-cn/site/dev/LICENSE | 201 --
documentations/3.0/zh-cn/site/dev/SPI/index.html | 984 -------
.../3.0/zh-cn/site/dev/SUMMARY/index.html | 830 ------
documentations/3.0/zh-cn/site/dev/TCK/index.html | 821 ------
documentations/3.0/zh-cn/site/dev/build/index.html | 864 ------
.../3.0/zh-cn/site/dev/checklist/index.html | 836 ------
.../3.0/zh-cn/site/dev/code-smell/index.html | 962 -------
.../3.0/zh-cn/site/dev/coding/index.html | 866 ------
.../3.0/zh-cn/site/dev/contract/index.html | 820 ------
.../3.0/zh-cn/site/dev/contribution/index.html | 1127 --------
.../3.0/zh-cn/site/dev/design/index.html | 905 ------
.../3.0/zh-cn/site/dev/implementation/index.html | 975 -------
.../3.0/zh-cn/site/dev/impls/cache/index.html | 883 ------
.../3.0/zh-cn/site/dev/impls/cluster/index.html | 877 ------
.../3.0/zh-cn/site/dev/impls/compiler/index.html | 858 ------
.../zh-cn/site/dev/impls/config-center/index.html | 893 ------
.../3.0/zh-cn/site/dev/impls/container/index.html | 865 ------
.../3.0/zh-cn/site/dev/impls/dispatcher/index.html | 865 ------
.../3.0/zh-cn/site/dev/impls/exchanger/index.html | 890 ------
.../site/dev/impls/exporter-listener/index.html | 866 ------
.../site/dev/impls/extension-factory/index.html | 860 ------
.../3.0/zh-cn/site/dev/impls/filter/index.html | 892 ------
.../zh-cn/site/dev/impls/introduction/index.html | 778 -----
.../site/dev/impls/invoker-listener/index.html | 865 ------
.../zh-cn/site/dev/impls/load-balance/index.html | 866 ------
.../zh-cn/site/dev/impls/logger-adapter/index.html | 883 ------
.../3.0/zh-cn/site/dev/impls/merger/index.html | 862 ------
.../3.0/zh-cn/site/dev/impls/monitor/index.html | 876 ------
.../3.0/zh-cn/site/dev/impls/networker/index.html | 862 ------
.../3.0/zh-cn/site/dev/impls/page/index.html | 864 ------
.../3.0/zh-cn/site/dev/impls/protocol/index.html | 951 -------
.../zh-cn/site/dev/impls/proxy-factory/index.html | 868 ------
.../3.0/zh-cn/site/dev/impls/registry/index.html | 1001 -------
.../3.0/zh-cn/site/dev/impls/remoting/index.html | 923 ------
.../3.0/zh-cn/site/dev/impls/router/index.html | 861 ------
.../3.0/zh-cn/site/dev/impls/serialize/index.html | 877 ------
.../zh-cn/site/dev/impls/status-checker/index.html | 867 ------
.../zh-cn/site/dev/impls/telnet-handler/index.html | 880 ------
.../3.0/zh-cn/site/dev/impls/threadpool/index.html | 863 ------
.../3.0/zh-cn/site/dev/impls/validation/index.html | 874 ------
documentations/3.0/zh-cn/site/dev/index.html | 782 -----
.../3.0/zh-cn/site/dev/introduction/index.html | 777 -----
.../site/dev/principals/code-detail/index.html | 844 ------
.../site/dev/principals/configuration/index.html | 890 ------
.../3.0/zh-cn/site/dev/principals/dummy/index.html | 1002 -------
.../site/dev/principals/expansibility/index.html | 814 ------
.../zh-cn/site/dev/principals/extension/index.html | 911 ------
.../dev/principals/general-knowledge/index.html | 863 ------
.../site/dev/principals/introduction/index.html | 778 -----
.../site/dev/principals/robustness/index.html | 864 ------
.../3.0/zh-cn/site/dev/release/index.html | 841 ------
.../zh-cn/site/dev/sources/images/close-expand.jpg | Bin 19287 -> 0 bytes
.../dev/sources/images/configuration-override.png | Bin 11422 -> 0 bytes
.../3.0/zh-cn/site/dev/sources/images/ddd.jpg | Bin 19358 -> 0 bytes
.../zh-cn/site/dev/sources/images/design-step1.png | Bin 121672 -> 0 bytes
.../zh-cn/site/dev/sources/images/design-step2.png | Bin 141298 -> 0 bytes
.../zh-cn/site/dev/sources/images/design-step3.png | Bin 165828 -> 0 bytes
.../zh-cn/site/dev/sources/images/design-step4.png | Bin 240786 -> 0 bytes
.../zh-cn/site/dev/sources/images/dubbo-export.jpg | Bin 70132 -> 0 bytes
.../site/dev/sources/images/dubbo-extension.jpg | Bin 112692 -> 0 bytes
.../site/dev/sources/images/dubbo-framework.jpg | Bin 219759 -> 0 bytes
.../site/dev/sources/images/dubbo-modules.jpg | Bin 25411 -> 0 bytes
.../site/dev/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../zh-cn/site/dev/sources/images/dubbo-refer.jpg | Bin 105967 -> 0 bytes
.../site/dev/sources/images/dubbo-relation.jpg | Bin 30304 -> 0 bytes
.../dev/sources/images/dubbo_protocol_header.png | Bin 74833 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_export.jpg | Bin 47624 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_invoke.jpg | Bin 45874 -> 0 bytes
.../site/dev/sources/images/dubbo_rpc_refer.jpg | Bin 50211 -> 0 bytes
.../site/dev/sources/images/event-listener.jpg | Bin 13192 -> 0 bytes
.../zh-cn/site/dev/sources/images/filter-chain.jpg | Bin 41029 -> 0 bytes
.../zh-cn/site/dev/sources/images/mix-api-spi.jpg | Bin 17004 -> 0 bytes
.../zh-cn/site/dev/sources/images/open-expand.jpg | Bin 10549 -> 0 bytes
.../site/dev/sources/images/seperate-api-spi.jpg | Bin 23683 -> 0 bytes
.../apache-dubbo-page_dev/index.html | 792 ------
.../label-an-issue-guide_dev/index.html | 801 ------
.../new-committer-guide_dev/index.html | 843 ------
.../committer-guide/release-guide_dev/index.html | 1175 --------
.../committer-guide/website-guide_dev/index.html | 781 -----
.../become-a-committer_dev/index.html | 784 -----
.../cla-signing-guide_dev/index.html | 800 ------
.../dubbo-extension-guide_dev/index.html | 811 ------
.../mailing-list-subscription-guide_dev/index.html | 857 ------
.../new-contributor-guide_dev/index.html | 804 ------
.../reporting-security-issues_dev/index.html | 790 ------
.../software-donation-guide_dev/index.html | 888 ------
.../test-coverage-guide_dev/index.html | 797 ------
.../site/developers/developers_dev/index.html | 1109 --------
.../3.0/zh-cn/site/developers/guide_dev/index.html | 853 ------
.../site/developers/user-guide/faq_dev/index.html | 792 ------
.../3.0/zh-cn/site/fonts/fontawesome-webfont.eot | Bin 37405 -> 0 bytes
.../3.0/zh-cn/site/fonts/fontawesome-webfont.svg | 399 ---
.../3.0/zh-cn/site/fonts/fontawesome-webfont.ttf | Bin 79076 -> 0 bytes
.../3.0/zh-cn/site/fonts/fontawesome-webfont.woff | Bin 43572 -> 0 bytes
documentations/3.0/zh-cn/site/img/favicon.ico | Bin 1150 -> 0 bytes
documentations/3.0/zh-cn/site/index.html | 811 ------
.../3.0/zh-cn/site/js/jquery-2.1.1.min.js | 4 -
.../3.0/zh-cn/site/js/modernizr-2.8.3.min.js | 1 -
documentations/3.0/zh-cn/site/js/theme.js | 105 -
documentations/3.0/zh-cn/site/search.html | 776 -----
documentations/3.0/zh-cn/site/search/lunr.js | 2986 --------------------
documentations/3.0/zh-cn/site/search/main.js | 96 -
.../3.0/zh-cn/site/search/search_index.json | 1 -
documentations/3.0/zh-cn/site/search/worker.js | 128 -
documentations/3.0/zh-cn/site/sitemap.xml | 718 -----
documentations/3.0/zh-cn/site/sitemap.xml.gz | Bin 278 -> 0 bytes
.../adaptive-extension/index.html | 1473 ----------
.../site/source_code_guide/cluster/index.html | 1316 ---------
.../site/source_code_guide/directory/index.html | 1269 ---------
.../site/source_code_guide/dubbo-spi/index.html | 1152 --------
.../source_code_guide/export-service/index.html | 2169 --------------
.../site/source_code_guide/loadbalance/index.html | 1504 ----------
.../source_code_guide/refer-service/index.html | 1617 -----------
.../zh-cn/site/source_code_guide/router/index.html | 1220 --------
.../service-invoking-process/index.html | 2703 ------------------
.../source_code_guide/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../images/consistent-hash-data-incline.jpg | Bin 101943 -> 0 bytes
.../sources/images/consistent-hash-invoker.jpg | Bin 87844 -> 0 bytes
.../sources/images/consistent-hash.jpg | Bin 95740 -> 0 bytes
.../sources/images/data-format.jpg | Bin 115165 -> 0 bytes
.../sources/images/directory-inherit-hierarchy.png | Bin 69024 -> 0 bytes
.../sources/images/dispatcher-location.jpg | Bin 89871 -> 0 bytes
.../sources/images/dubbo-spi-result.jpg | Bin 33007 -> 0 bytes
.../sources/images/java-spi-result.jpg | Bin 46805 -> 0 bytes
.../sources/images/request-id-application.jpg | Bin 217379 -> 0 bytes
.../sources/images/send-request-process.jpg | Bin 83592 -> 0 bytes
.../sources/images/send-request-thread-stack.jpg | Bin 213679 -> 0 bytes
.../sources/images/service-registry.png | Bin 57116 -> 0 bytes
documentations/3.0/zh-cn/site/user/LICENSE | 201 --
.../3.0/zh-cn/site/user/SUMMARY/index.html | 901 ------
.../3.0/zh-cn/site/user/benchmark-tool/index.html | 804 ------
.../3.0/zh-cn/site/user/best-practice/index.html | 851 ------
.../3.0/zh-cn/site/user/capacity-plan/index.html | 823 ------
.../site/user/configuration/annotation/index.html | 882 ------
.../zh-cn/site/user/configuration/api/index.html | 922 ------
.../user/configuration/config-center/index.html | 884 ------
.../configuration-load-process/index.html | 970 -------
.../configuration/environment-variables/index.html | 841 ------
.../3.0/zh-cn/site/user/configuration/index.html | 782 -----
.../configuration/properties-deprecated/index.html | 803 ------
.../site/user/configuration/properties/index.html | 806 ------
.../zh-cn/site/user/configuration/xml/index.html | 940 ------
.../3.0/zh-cn/site/user/coveragence/index.html | 787 ------
.../demos/GooglePb-generic-reference/index.html | 856 ------
.../3.0/zh-cn/site/user/demos/accesslog/index.html | 812 ------
.../user/demos/async-call-deprecated/index.html | 822 ------
.../zh-cn/site/user/demos/async-call/index.html | 912 ------
.../demos/async-execute-on-provider/index.html | 881 ------
.../zh-cn/site/user/demos/attachment/index.html | 832 ------
.../3.0/zh-cn/site/user/demos/auth/index.html | 799 ------
.../site/user/demos/callback-parameter/index.html | 914 ------
.../site/user/demos/concurrency-control/index.html | 856 ------
.../site/user/demos/config-connections/index.html | 798 ------
.../user/demos/config-rule-deprecated/index.html | 814 ------
.../zh-cn/site/user/demos/config-rule/index.html | 991 -------
.../site/user/demos/consumer-threadpool/index.html | 806 ------
.../3.0/zh-cn/site/user/demos/context/index.html | 844 ------
.../zh-cn/site/user/demos/delay-publish/index.html | 853 ------
.../user/demos/distributed-transaction/index.html | 807 ------
.../3.0/zh-cn/site/user/demos/dump/index.html | 815 ------
.../zh-cn/site/user/demos/echo-service/index.html | 821 ------
.../zh-cn/site/user/demos/events-notify/index.html | 901 ------
.../site/user/demos/explicit-target/index.html | 839 ------
.../user/demos/fault-tolerent-strategy/index.html | 860 ------
.../site/user/demos/generic-reference/index.html | 894 ------
.../site/user/demos/generic-service/index.html | 847 ------
.../site/user/demos/graceful-shutdown/index.html | 833 ------
.../zh-cn/site/user/demos/group-merger/index.html | 846 ------
.../site/user/demos/hostname-binding/index.html | 891 ------
.../3.0/zh-cn/site/user/demos/index.html | 782 -----
.../zh-cn/site/user/demos/introduction/index.html | 780 -----
.../zh-cn/site/user/demos/lazy-connect/index.html | 809 ------
.../zh-cn/site/user/demos/loadbalance/index.html | 858 ------
.../zh-cn/site/user/demos/local-call/index.html | 841 ------
.../zh-cn/site/user/demos/local-mock/index.html | 879 ------
.../zh-cn/site/user/demos/local-stub/index.html | 838 ------
.../site/user/demos/logger-strategy/index.html | 822 ------
.../site/user/demos/multi-protocols/index.html | 848 ------
.../site/user/demos/multi-registry/index.html | 880 ------
.../site/user/demos/multi-versions/index.html | 832 ------
.../3.0/zh-cn/site/user/demos/netty4/index.html | 829 ------
.../user/demos/parameter-validation/index.html | 977 -------
.../site/user/demos/preflight-check/index.html | 847 ------
.../zh-cn/site/user/demos/protobuf-idl/index.html | 804 ------
.../user/demos/reference-config-cache/index.html | 802 ------
.../zh-cn/site/user/demos/registry-only/index.html | 814 ------
.../zh-cn/site/user/demos/result-cache/index.html | 831 ------
.../user/demos/routing-rule-deprecated/index.html | 925 ------
.../zh-cn/site/user/demos/routing-rule/index.html | 1036 -------
.../zh-cn/site/user/demos/serialization/index.html | 876 ------
.../site/user/demos/service-container/index.html | 861 ------
.../site/user/demos/service-downgrade/index.html | 817 ------
.../zh-cn/site/user/demos/service-group/index.html | 828 ------
.../3.0/zh-cn/site/user/demos/set-host/index.html | 832 ------
.../user/demos/simplify-registry-data/index.html | 1125 --------
.../site/user/demos/static-service/index.html | 818 ------
.../zh-cn/site/user/demos/stickiness/index.html | 814 ------
.../site/user/demos/subscribe-only/index.html | 814 ------
.../zh-cn/site/user/demos/thread-model/index.html | 827 ------
.../3.0/zh-cn/site/user/demos/tls/index.html | 809 ------
.../site/user/demos/token-authorization/index.html | 825 ------
.../3.0/zh-cn/site/user/dependencies/index.html | 858 ------
documentations/3.0/zh-cn/site/user/index.html | 783 -----
.../user/languages/erlang/reference/index.html | 790 ------
.../user/languages/erlang/serialization/index.html | 805 ------
.../site/user/languages/erlang/service/index.html | 820 ------
.../site/user/languages/erlang/start/index.html | 824 ------
.../3.0/zh-cn/site/user/maturity/index.html | 1412 ---------
.../site/user/new-features-in-a-glance/index.html | 901 ------
.../3.0/zh-cn/site/user/perf-test/index.html | 998 -------
.../site/user/preface/architecture/index.html | 925 ------
.../zh-cn/site/user/preface/background/index.html | 826 ------
.../3.0/zh-cn/site/user/preface/index.html | 782 -----
.../site/user/preface/requirements/index.html | 783 -----
.../3.0/zh-cn/site/user/preface/usage/index.html | 841 ------
.../3.0/zh-cn/site/user/quick-start/index.html | 911 ------
.../3.0/zh-cn/site/user/recommend/index.html | 947 -------
.../3.0/zh-cn/site/user/references/api/index.html | 821 ------
.../zh-cn/site/user/references/maven/index.html | 819 ------
.../references/metadata/introduction/index.html | 1087 -------
.../references/metadata/metadata-redis/index.html | 804 ------
.../metadata/metadata-zookeeper/index.html | 804 ------
.../site/user/references/protocol/dubbo/index.html | 929 ------
.../site/user/references/protocol/gRPC/index.html | 791 ------
.../user/references/protocol/hessian/index.html | 868 ------
.../site/user/references/protocol/http/index.html | 860 ------
.../references/protocol/introduction/index.html | 778 -----
.../user/references/protocol/memcached/index.html | 806 ------
.../site/user/references/protocol/redis/index.html | 806 ------
.../site/user/references/protocol/rest/index.html | 1379 ---------
.../site/user/references/protocol/rmi/index.html | 883 ------
.../user/references/protocol/thrift/index.html | 839 ------
.../user/references/protocol/webservice/index.html | 863 ------
.../3.0/zh-cn/site/user/references/qos/index.html | 1019 -------
.../references/registry/introduction/index.html | 778 -----
.../user/references/registry/multicast/index.html | 836 ------
.../site/user/references/registry/nacos/index.html | 858 ------
.../site/user/references/registry/redis/index.html | 873 ------
.../user/references/registry/simple/index.html | 848 ------
.../user/references/registry/zookeeper/index.html | 919 ------
.../zh-cn/site/user/references/telnet/index.html | 896 ------
.../references/xml/dubbo-application/index.html | 901 ------
.../user/references/xml/dubbo-argument/index.html | 856 ------
.../references/xml/dubbo-config-center/index.html | 937 ------
.../user/references/xml/dubbo-consumer/index.html | 1001 -------
.../user/references/xml/dubbo-method/index.html | 986 -------
.../user/references/xml/dubbo-module/index.html | 861 ------
.../user/references/xml/dubbo-monitor/index.html | 841 ------
.../user/references/xml/dubbo-parameter/index.html | 850 ------
.../user/references/xml/dubbo-protocol/index.html | 1061 -------
.../user/references/xml/dubbo-provider/index.html | 1261 ---------
.../user/references/xml/dubbo-reference/index.html | 1091 -------
.../user/references/xml/dubbo-registry/index.html | 1001 -------
.../user/references/xml/dubbo-service/index.html | 1131 --------
.../user/references/xml/introduction/index.html | 788 ------
documentations/3.0/zh-cn/site/user/rest/index.html | 1776 ------------
.../3.0/zh-cn/site/user/serialization/index.html | 1041 -------
.../3.0/zh-cn/site/user/simple-monitor/index.html | 841 ------
.../3.0/zh-cn/site/user/sources/images/1kres.png | Bin 39384 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/1ktps.png | Bin 38814 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/200kres.png | Bin 39229 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/200ktps.png | Bin 38997 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/50kres.png | Bin 39733 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/50ktps.png | Bin 39723 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/arch.png | Bin 15546 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/cluster.jpg | Bin 32874 -> 0 bytes
.../site/user/sources/images/code-coverage.jpg | Bin 141776 -> 0 bytes
.../site/user/sources/images/code-dependency.jpg | Bin 138868 -> 0 bytes
.../site/user/sources/images/code-quality1.jpg | Bin 56913 -> 0 bytes
.../site/user/sources/images/code-quality5.jpg | Bin 41672 -> 0 bytes
.../site/user/sources/images/code-tendency.jpg | Bin 54729 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/context.png | Bin 46114 -> 0 bytes
.../sources/images/dubbo-architecture-future.jpg | Bin 55605 -> 0 bytes
.../sources/images/dubbo-architecture-roadmap.jpg | Bin 33931 -> 0 bytes
.../user/sources/images/dubbo-architecture.jpg | Bin 18810 -> 0 bytes
.../user/sources/images/dubbo-config-override.jpg | Bin 68132 -> 0 bytes
.../site/user/sources/images/dubbo-config.jpg | Bin 69630 -> 0 bytes
.../site/user/sources/images/dubbo-directly.jpg | Bin 38922 -> 0 bytes
.../sources/images/dubbo-properties-override.jpg | Bin 24590 -> 0 bytes
.../site/user/sources/images/dubbo-protocol.jpg | Bin 19340 -> 0 bytes
.../user/sources/images/dubbo-redis-registry.jpg | Bin 47205 -> 0 bytes
.../sources/images/dubbo-service-governance.jpg | Bin 67000 -> 0 bytes
.../zh-cn/site/user/sources/images/dubbo-token.jpg | Bin 17153 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/future.jpg | Bin 20793 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/jta-xa.jpg | Bin 37931 -> 0 bytes
.../site/user/sources/images/lock-get-bean.jpg | Bin 109801 -> 0 bytes
.../site/user/sources/images/lock-init-context.jpg | Bin 39227 -> 0 bytes
.../zh-cn/site/user/sources/images/multicast.jpg | Bin 20269 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/pojores.png | Bin 37733 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/pojotps.png | Bin 39797 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/rest.jpg | Bin 206610 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/rt.png | Bin 31098 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/stub.jpg | Bin 28646 -> 0 bytes
.../site/user/sources/images/subscribe-only.jpg | Bin 20626 -> 0 bytes
...pg-version=1&modificationDate=1326468174000.jpg | Bin 20626 -> 0 bytes
.../3.0/zh-cn/site/user/sources/images/tps.png | Bin 33114 -> 0 bytes
.../zh-cn/site/user/sources/images/zookeeper.jpg | Bin 31272 -> 0 bytes
.../3.0/zh-cn/site/user/versions/index.html | 783 -----
.../site/user/versions/version-270/index.html | 1095 -------
en-us/css/dropdown.css | 48 +
google7362984ffdc17d37.html | 1 -
gulpfile.js | 65 -
overrides/partials/header.html | 87 +
overrides/partials/language-change.html | 44 +
overrides/partials/nav-item.html | 112 +
overrides/partials/nav.html | 70 +
overrides/partials/tabs-item.html | 104 +
package.json | 57 -
redirect.ejs | 33 -
schema/dubbo/dubbo.xsd | 1271 ---------
site_config/blog.js | 637 -----
site_config/community.jsx | 871 ------
site_config/develop.js | 181 --
site_config/docs.js | 1418 ----------
site_config/ecology.js | 2892 -------------------
site_config/home.jsx | 188 --
site_config/site.js | 235 --
sitemap.xml | 1609 -----------
src/components/bar/index.jsx | 29 -
src/components/bar/index.scss | 59 -
src/components/button/index.jsx | 23 -
src/components/button/index.scss | 23 -
src/components/footer/index.jsx | 68 -
src/components/footer/index.scss | 111 -
src/components/header/index.jsx | 204 --
src/components/header/index.scss | 247 --
src/components/language/index.jsx | 38 -
src/components/pageSlider/index.jsx | 143 -
src/components/pageSlider/index.scss | 34 -
src/components/sidemenu/index.jsx | 62 -
src/components/sidemenu/index.scss | 121 -
src/components/sidemenu/item.jsx | 93 -
src/components/slider/index.jsx | 166 --
src/components/slider/index.scss | 30 -
src/fonts/TXD_D-Medium.eot | Bin 5025 -> 0 bytes
src/fonts/TXD_D-Medium.ttf | Bin 8984 -> 0 bytes
src/fonts/TXD_D-Medium.woff | Bin 5488 -> 0 bytes
src/fonts/TXD_D-Regular.eot | Bin 4837 -> 0 bytes
src/fonts/TXD_D-Regular.ttf | Bin 8832 -> 0 bytes
src/fonts/TXD_D-Regular.woff | Bin 5336 -> 0 bytes
src/markdown.scss | 807 ------
src/pages/blog/blogItem.jsx | 57 -
src/pages/blog/blogItem.scss | 57 -
src/pages/blog/index.jsx | 58 -
src/pages/blog/index.scss | 55 -
src/pages/blogDetail/index.jsx | 112 -
src/pages/blogDetail/index.scss | 11 -
src/pages/community/contactItem.jsx | 45 -
src/pages/community/contributorItem.jsx | 15 -
src/pages/community/ecoItem.jsx | 31 -
src/pages/community/eventCard.jsx | 25 -
src/pages/community/index.jsx | 82 -
src/pages/community/index.scss | 189 --
src/pages/documentation/index.jsx | 124 -
src/pages/documentation/index.scss | 36 -
src/pages/ecology/card.jsx | 13 -
src/pages/ecology/img-item.jsx | 65 -
src/pages/ecology/index.jsx | 107 -
src/pages/ecology/index.scss | 291 --
src/pages/ecology/memo.jsx | 56 -
src/pages/home/featureItem.jsx | 16 -
src/pages/home/index.jsx | 147 -
src/pages/home/index.scss | 488 ----
src/reset.scss | 10 -
src/variables.scss | 24 -
template.ejs | 32 -
utils/index.js | 28 -
webpack.config.js | 76 -
zh-cn/css/dropdown.css | 48 +
3343 files changed, 514 insertions(+), 910598 deletions(-)
diff --git a/.docsite b/.docsite
deleted file mode 100644
index e69de29..0000000
diff --git a/.gitignore b/.gitignore
index 8b7e577..5a34cf7 100644
--- a/.gitignore
+++ b/.gitignore
@@ -5,8 +5,7 @@ npm-debug.log
*.orig
package-lock.json
*.iml
-/en-us/
-/zh-cn/
build/
index.html
md_json/
+site/
diff --git a/blog/en-us/apachecon-na-2018.md b/blog/en-us/apachecon-na-2018.md
deleted file mode 100644
index cd61182..0000000
--- a/blog/en-us/apachecon-na-2018.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: The ApacheCon NA schedule has been announced
-keywords: Dubbo, ApacheCon NA
-description: This article will introduce you that the ApacheCon NA schedule has been announced attention.
----
-
-The ApacheCon NA schedule has been announced
----
-
-Ian Luo(PMC) and Jun Liu(PMC) will talk about "Introducing Apache Dubbo(Incubating): What is Dubbo and How it Works" at ApacheCon NA this year in Montréal! Please check out the schedule [here](https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/b8db9dc580d85853f) and register [here](https://www.eventbrite.com/e/apachecon-north-america-2018-registration-43200327342).
diff --git a/blog/en-us/download.md b/blog/en-us/download.md
deleted file mode 100644
index 37f6813..0000000
--- a/blog/en-us/download.md
+++ /dev/null
@@ -1,178 +0,0 @@
----
-title: Downloads
-keywords: Dubbo, Downloads, Version
-description: This article will introduce you how to understand the details of each version and upgrade matters needing attention.
----
-
-
-# Downloads
-
-## Verification
-
-you can follow these [procedures](https://www.apache.org/info/verification) and the [KEYS](https://www.apache.org/dist/dubbo/KEYS) file to verify the download files
-
-## Apache Dubbo
-
-> GitHub: https://github.com/apache/dubbo \
-> Release Notes: https://github.com/apache/dubbo/releases
-
-### 2.7.7 (2020-05-18)
-
-* [source](https://www.apache.org/dyn/closer.cgi?path=dubbo/2.7.7/apache-dubbo-2.7.7-src.zip) |
-[asc](https://www.apache.org/dist/dubbo/2.7.7/apache-dubbo-2.7.7-src.zip.asc) |
-[sha512](https://www.apache.org/dist/dubbo/2.7.7/apache-dubbo-2.7.7-src.zip.sha512)
-
-### 2.7.5 (2019-12-29)
-
-* [source](https://www.apache.org/dyn/closer.cgi?path=dubbo/2.7.5/apache-dubbo-2.7.5-src.zip) |
-[asc](https://www.apache.org/dist/dubbo/2.7.5/apache-dubbo-2.7.5-src.zip.asc) |
-[sha512](https://www.apache.org/dist/dubbo/2.7.5/apache-dubbo-2.7.5-src.zip.sha512)
-
-### 2.7.4.1 (2019-10-27)
-
-* [source](https://www.apache.org/dyn/closer.cgi?path=dubbo/2.7.4.1/apache-dubbo-2.7.4.1-src.zip) |
-[asc](https://www.apache.org/dist/dubbo/2.7.4.1/apache-dubbo-2.7.4.1-src.zip.asc) |
-[sha512](https://www.apache.org/dist/dubbo/2.7.4.1/apache-dubbo-2.7.4.1-src.zip.sha512)
-
-### 2.7.4 (2019-10-19)
-
-* [source](https://www.apache.org/dyn/closer.cgi?path=dubbo/2.7.4/apache-dubbo-2.7.4-src.zip) |
-[asc](https://www.apache.org/dist/dubbo/2.7.4/apache-dubbo-2.7.4-src.zip.asc) |
-[sha512](https://www.apache.org/dist/dubbo/2.7.4/apache-dubbo-2.7.4-src.zip.sha512)
-
-### 2.7.3 (2019-07-19)
-
-* [source](https://www.apache.org/dyn/closer.cgi?path=dubbo/2.7.3/apache-dubbo-2.7.3-src.zip) |
-[asc](https://www.apache.org/dist/dubbo/2.7.3/apache-dubbo-2.7.3-src.zip.asc) |
-[sha512](https://www.apache.org/dist/dubbo/2.7.3/apache-dubbo-2.7.3-src.zip.sha512)
-
-### 2.7.2 (2019-06-06)
-
-* [source](https://archive.apache.org/dist/dubbo/2.7.2/apache-dubbo-2.7.2-src.zip) |
-[asc](https://archive.apache.org/dist/dubbo/2.7.2/apache-dubbo-2.7.2-src.zip.asc) |
-[sha512](https://archive.apache.org/dist/dubbo/2.7.2/apache-dubbo-2.7.2-src.zip.sha512)
-
-### 2.7.1 (2019-03-26)
-
-* [source](https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-src.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-src.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-src.zip.sha512)
-* [binary](https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-bin.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-bin.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.7.1/apache-dubbo-incubating-2.7.1-bin.zip.sha512)
-
-
-### 2.7.0 (2019-01-29)
-
-* [source](https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-source-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-source-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-source-release.zip.sha512)
-* [binary](https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-bin-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-bin-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.7.0/apache-dubbo-incubating-2.7.0-bin-release.zip.sha512)
-
-### 2.6.7 (2019-07-15)
-
-* [source](https://www.apache.org/dist/dubbo/2.6.7/apache-dubbo-2.6.7-source-release.zip) |
-[asc](https://www.apache.org/dist/dubbo/2.6.7/apache-dubbo-2.6.7-source-release.zip.asc) |
-[sha512](https://www.apache.org/dist/dubbo/2.6.7/apache-dubbo-2.6.7-source-release.zip.sha512)
-* [binary](https://www.apache.org/dist/dubbo/2.6.7/apache-dubbo-2.6.7-bin-release.zip) |
-[asc](https://www.apache.org/dist/dubbo/2.6.7/apache-dubbo-2.6.7-bin-release.zip.asc) |
-[sha512](https://www.apache.org/dist/dubbo/2.6.7/apache-dubbo-2.6.7-bin-release.zip.sha512)
-
-### 2.6.6 (2019-03-07)
-
-* [source](https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-source-release.zip) |
-[asc](https://www.apache.org/dist/incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-source-release.zip.asc) |
-[sha512](https://www.apache.org/dist/incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-source-release.zip.sha512)
-* [binary](https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-bin-release.zip) |
-[asc](https://www.apache.org/dist/incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-bin-release.zip.asc) |
-[sha512](https://www.apache.org/dist/incubator/dubbo/2.6.6/apache-dubbo-incubating-2.6.6-bin-release.zip.sha512)
-
-### 2.6.5 (2018-11-23)
-
-* [source](https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-source-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-source-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-source-release.zip.sha512)
-* [binary](https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-bin-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-bin-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.6.5/apache-dubbo-incubating-2.6.5-bin-release.zip.sha512)
-
-### 2.6.4 (2018-10-08)
-
-* [source](https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-source-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-source-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-source-release.zip.sha512)
-* [binary](https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-bin-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-bin-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.6.4/apache-dubbo-incubating-2.6.4-bin-release.zip.sha512)
-
-### 2.6.3 (2018-09-11)
-
-* [source](https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-source-release.zip.sha512)
-* [binary](https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.6.3/apache-dubbo-incubating-2.6.3-bin-release.zip.sha512)
-
-### 2.6.2 (2018-06-07)
-
-* [source](https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip.sha512)
-* [binary](https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-bin-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-bin-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-bin-release.zip.sha512)
-
-## Dubbo Spring Boot Starter
-
-> GitHub: https://github.com/apache/incubator-dubbo-spring-boot-project \
-> Release Notes: https://github.com/apache/incubator-dubbo-spring-boot-project/releases
-
-### 2.7.1 (2019-04-09)
-
-* [source](https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-source-release.zip) |
-[asc](https://www.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-source-release.zip.asc) |
-[sha512](https://www.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-source-release.zip.sha512)
-* [binary](https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-bin-release.zip) |
-[asc](https://www.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-bin-release.zip.asc) |
-[sha512](https://www.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.1/apache-dubbo-spring-boot-project-incubating-2.7.1-bin-release.zip.sha512)
-
-### 2.7.0 (2019-02-14)
-
-* [source](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-source-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-source-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-source-release.zip.sha512)
-* [binary](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-bin-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-bin-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/2.7.0/apache-dubbo-spring-boot-project-incubating-2.7.0-bin-release.zip.sha512)
-
-### 0.2.1 (2019-01-27)
-
-* [source](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-source-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-source-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-source-release.zip.sha512)
-* [binary](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-bin-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-bin-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.2.1/apache-dubbo-spring-boot-project-incubating-0.2.1-bin-release.zip.sha512)
-
-### 0.1.2 (2019-01-27)
-
-* [source](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-source-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-source-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-source-release.zip.sha512)
-* [binary](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-bin-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-bin-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/spring-boot-project/0.1.2/apache-dubbo-spring-boot-project-incubating-0.1.2-bin-release.zip.sha512)
-
-## Dubbo Admin
-
-> GitHub: https://github.com/apache/incubator-dubbo-admin \
-> Release Notes: https://github.com/apache/incubator-dubbo-admin/releases
-
-### 0.1 (2019-02-15)
-
-* [source](https://archive.apache.org/dist/incubator/dubbo/dubbo-ops/0.1/apache-dubbo-ops-incubating-0.1-source-release.zip) |
-[asc](https://archive.apache.org/dist/incubator/dubbo/dubbo-ops/0.1/apache-dubbo-ops-incubating-0.1-source-release.zip.asc) |
-[sha512](https://archive.apache.org/dist/incubator/dubbo/dubbo-ops/0.1/apache-dubbo-ops-incubating-0.1-source-release.zip.sha512)
diff --git a/blog/en-us/dubbo-101.md b/blog/en-us/dubbo-101.md
deleted file mode 100644
index 41f42b7..0000000
--- a/blog/en-us/dubbo-101.md
+++ /dev/null
@@ -1,390 +0,0 @@
----
-title: Your First Dubbo Demo
-keywords: Dubbo, RPC, RMI
-description: Modern distributed frameworks is similiar to RMI in terms of concepts. They both use Java interface as a service contract, archive service registry and discovery by a registry center, and Shield communication details by a proxy.
----
-
-# Your First Dubbo Demo
-
-## Java RMI Introduction
-
-Java RMI (Remote Method Invocation) is a mechanism that allows users to access or invocate an object and a method running on another JVM (Java Virtual Machine). RMI is an implementation of RPC (Remote Procedure Call) in java with support of OOP (Object Oriented Paradigms). Instead of bothering IDL (Interface Define Language), users can build distributed applications by depending on interfaces in an easy and natural way.
-
-### Java RMI Work Flow
-
-Here is how a typical RMI invocation usually works:
-
-1. The server registers service from RMI and binds its address.
-2. The client registers service from RMI and obtains target address.
-3. The client invokes methods of local stub object in the same way of invoking other local objects.
-4. Local stub object zips invoking information and send it to the server via network.
-5. The Skeleton object of server receives the network request and unzips the information.
-6. Server runs invocation on the target object based on the information and return the zipped results back to client via network.
-
-
-
-
-(source：https://www.cs.rutgers.edu/~pxk/417/notes/images/rpc-rmi_flow.png)
-
-### Java RMI Concepts
-
-Java RMI is a technique foundation stone of creating distributed applications in Java. The following EJB techniques and current framework of distributed services still inherit the fundamental concepts of Java RMI. In RMI invocation, there are some core concepts：
-
-1. The invocation is run remotely on **interface**.
-2. Disguise remote invocation as local invocation by **Stub object** on client and **Skeleton object** on server.
-3. The service is registered and looked up by **RMI** registry service.
-
-For 1. users are dependent on interfaces which should be implemented by server.
-
-For 2. In J2SE 1.5 version and before, it needs to pre-compile Stub on client and Skeleton on server by rmic. In the later versions there is no need to do so.
-
-The following is a code example of registry and look-up in RMI.
-
-#### Server service registry
-
-```java
-Hello obj = new HelloImpl(); // #1
-Hello stub = (Hello) UnicastRemoteObject.exportObject(obj, 0); // #2
-Registry registry = LocateRegistry.createRegistry(1099); // #3
-registry.rebind("Hello", stub); // #4
-```
-
-Notes:
-
-1. Initiate service object instance.
-
-2. Create stub object to communicate with the server by UnicastRemoteObject.exportObject.
-
-3. Create a local RMI registry service on port 1099 which is run on server. It can also be registered as an independent process.
-
-4. Bind stub object into registry so the client can find the remote object by looking up Hello.
-
-
-#### Client service look-up
-
-```java
-Registry registry = LocateRegistry.getRegistry(); // #1
-Hello stub = (Hello) registry.lookup("Hello"); // #2
-String response = stub.sayHello(); // #3
-```
-
-Notes:
-
-1. Acquire registry service instances. In this case, there is no input parameters so it is assumed that the acquired instance is located on port 1099.
-2. Look up the remote object named Hello in registry service.
-3. Run a RMI invocation via acquired Stub object and get results.
-Understand the work flow and basic concepts of RMI is helpful to handle current framework of distributed service. It is recommended to refer to RMI official documents for further information[^1].
-
-## Basic Concepts of Dubbo
-
-The basic concepts of current framework of distributed service is similar to the one of RMI. They both use Java interface as service contract, register and look up by registry center and use agency to block the details of remote communications. Specifically, Dubbo has following four types of roles to play when running：
-
-1. Serve the provider – Expose service at assigned ports at initialization and register the service address and ports at registry center
-2. Serve the consumer – Subscribe the service of interests at registry center at initialization to acquire the list of addresses provided by the service provider.
-3. Registry center – Register and look up service. Store the address provided by the service provider and send it to the consumer.
-4. Monitor center – Collect and monitor running status of providers and consumers, e.g., times of invocations, delay of invocations, etc.
-5. Running container – Initialize and load the provider and manage the lifecycle of running.
-
-
-
-
-
-
-**Deploy stage**
-
-* Service providers expose service at assigned ports and register information of service at registry center.
-* Service consumers subscribe the list of service addresses from registry center.
-
-**Run stage**
-
-* Registry center sends the address to service consumers.
-* After receiving the list of addresses, service consumers select one of them and invoke an object service.
-* During invocation, the running status of service providers and consumers is reported to the monitor center.
-
-## Dubbo Applications Based on API
-
-The applications of Dubbo are usually assembled by Spring. To obtain an available Dubbo application quickly, the example shown here abandons complex configurations but to create service provider and consumer in Dubbo API oriented way. Additionally, the registry center and monitor center do not need installation or configuration in this example.
-
-In production environment, the service of Dubbo usually requires cooperation with a distributed service registry center, such as ZooKeeper. For convenience, Dubbo offers two ways to avoid extra work of building registry center, namely direct connection [2] and assembled podcast [3] respectively. In this example, the latter way is applied to register and look up service.
-
-### Define Service Contract
-
-```java
-public interface GreetingsService {
- String sayHi(String name); // #1
-}
-```
-
-**Notes**：
-
-1. The codes define a simple service contract where there is only one function, sayHi, can be invoked. The type of input parameter and return value are both String.
-
-### Provide Contract Implementation
-
-```java
-public class GreetingsServiceImpl implements GreetingsService { // #1
- @Override
- public String sayHi(String name) {
- return "hi, " + name; // #2
- }
-}
-```
-
-**Notes**：
-
-1. Service providers need to implement the interface of service contract, GreetingsService.
-2. This function simply returns a welcome message. For example, if the input value is *dubbo*，it will return *hi, dubbo*.
-
-### Implement Dubbo Service Provider
-
-```java
-public class Application {
- public static void main(String[] args) throws IOException {
- ServiceConfig<GreetingsService> service = new ServiceConfig<>(); // #1
- service.setApplication(new ApplicationConfig("first-dubbo-provider")); // #2
- service.setRegistry(new RegistryConfig("multicast://224.5.6.7:1234")); // #3
- service.setInterface(GreetingsService.class); // #4
- service.setRef(new GreetingsServiceImpl()); // #5
- service.export(); // #6
- System.in.read(); // #7
- }
-}
-```
-
-**Notes**：
-
-1. Create an instance *ServiceConfig* with service interface type as generics parameters, which is *GreetingsService* in this example.
-2. Generate an instance of *ApplicationConfig* and assemble it into *ServiceConfig*.
-3. Generate an instance *RegistryConfig* and assemble it into *ServiceConfig*. Since the assembled way is applied here, the parameter should be `multicast://224.5.6.7:1234`. The valid range of assembled address is *224.0.0.0 - 239.255.255.255*
-4. Assemble the service contract *GreetingsService* into *ServiceConfig*.
-5. Assemble the instance with implementation of *GreetingsServicelmpl* provided by service providers into *ServiceConfig*.
-6. *ServiceConfig* starts to expose itself at default ports *20880*. after being equipped with enough information.
-7. Press any key or *ctrl-C* to exit to avoid server halt.
-
-
-### Implement Dubbo Service Consumer
-
-```java
-public class Application {
- public static void main(String[] args) {
- ReferenceConfig<GreetingsService> reference = new ReferenceConfig<>(); // #1
- reference.setApplication(new ApplicationConfig("first-dubbo-client")); // #2
- reference.setRegistry(new RegistryConfig("multicast://224.5.6.7:1234")); // #3
- reference.setInterface(GreetingsService.class); // #4
- GreetingsService greetingsService = reference.get(); // #5
- String message = greetingsService.sayHi("dubbo"); // #6
- System.out.println(message); // #7
- }
-}
-```
-
-**Notes**：
-
-1. Create an instance of *ReferenceConfig* with service interface type as generics parameters, which is *GreetingsService* in this example.
-2. Create an instance of *ApplicationConfig*, and assemble it into *ReferenceConfig*.
-3. Generate an instance *RegistryConfig*, and assemble it into *ReferenceConfig*. Note that the address information here should be the same as the one of the service provider.
-4. Assemble the service contract *GreetingsService* into *ReferenceConfig*.
-5. Obtain the agency of *GreetingsService* from *ReferenceConfig*.
-6. Invoke a remote call through *GreetingsSerive*’s agency and pass in `dubbo` as input parameter.
-7. Return and print results `hi, dubbo`.
-
-
-### Run
-
-The complete example can be found at https://github.com/apache/dubbo-samples/tree/master/java/dubbo-samples-api. In the complete version, it is convenient to execute by maven in command line with the configuration of *exec-maven-plugin*. Of course, it can also be executed directly in IDE. However, there is one noteworthy thing that because of using assembled way to look up service, it needs to assign *-Djava.net.preferIPv4Stack=true* when running.
-
-#### Build Example
-
-Synchronize the example codes and build by the following command lines:
-
-1. Synchronize the example codes: git clone https://github.com/apache/dubbo-samples.git
-2. Build：mvn clean package
-
-```bash
-$ git clone https://github.com/apache/dubbo-samples.git
-$ cd dubbo-samples/java/dubbo-samples-api/
-$ mvn clean package
-INFO] Scanning for projects...
-[INFO]
-[INFO] ------------------------------------------------------------------------
-[INFO] Building dubbo-samples-api 1.0-SNAPSHOT
-[INFO] ------------------------------------------------------------------------
-[INFO]
-[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ dubbo-samples-api ---
-...
-[INFO] ------------------------------------------------------------------------
-[INFO] BUILD SUCCESS
-[INFO] ------------------------------------------------------------------------
-[INFO] Total time: 2.182 s
-[INFO] Finished at: 2018-05-28T14:56:08+08:00
-[INFO] Final Memory: 20M/353M
-[INFO] ------------------------------------------------------------------------
-```
-
-The build is finished when it shows `BUILD SUCCESS`. Then comes the running stage.
-
-#### Run the server
-
-Run the service provider by the following maven command lines:
-
-```bash
-$ mvn -Djava.net.preferIPv4Stack=true -Dexec.mainClass=org.apache.dubbo.samples.provider.Application exec:java
-[INFO] Scanning for projects...
-[INFO]
-[INFO] ------------------------------------------------------------------------
-[INFO] Building dubbo-samples-api 1.0-SNAPSHOT
-[INFO] ------------------------------------------------------------------------
-[INFO]
-[INFO] --- exec-maven-plugin:1.6.0:java (default-cli) @ dubbo-samples-api ---
-log4j:WARN No appenders could be found for logger (org.apache.dubbo.common.logger.LoggerFactory).
-log4j:WARN Please initialize the log4j system properly.
-log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
-first-dubbo-provider is running.
-```
-
-When *first-dubbo-provider is running* appears, the service provider is ready to be called by the client.
-
-#### Run the client
-
-Run the service consumer by the following maven command lines:
-
-```bash
-$ mvn -Djava.net.preferIPv4Stack=true -Dexec.mainClass=org.apache.dubbo.samples.consumer.Application exec:java
-[INFO] Scanning for projects...
-[INFO]
-[INFO] ------------------------------------------------------------------------
-[INFO] Building dubbo-samples-api 1.0-SNAPSHOT
-[INFO] ------------------------------------------------------------------------
-[INFO]
-[INFO] --- exec-maven-plugin:1.6.0:java (default-cli) @ dubbo-samples-api ---
-log4j:WARN No appenders could be found for logger (org.apache.dubbo.common.logger.LoggerFactory).
-log4j:WARN Please initialize the log4j system properly.
-log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
-hi, dubbo
-```
-
-`hi, dubbo` is the execution results from service provider.
-
-## Quick Creation of A Dubbo Application
-
-Dubbo also provides a public platform that can create a Dubbo application quickly based on Spring Boot. Visit http://start.dubbo.io and follow the figure below to create an example project:
-
-
-
-**Notes**：
-
-1. Provide maven groupId in *Group* with default value `com.example`.
-2. Provide maven artifactId in *Artifact* with default value `demo`.
-3. Provide the name of service in *DubboServiceName* with default value `com.example.HelloService`.
-4. Provide the version of service in *DubboServiceVersion* with default value `1.0.0`.
-5. Choose server or client in *Client/Server* with default value `server`.
-6. *embeddedZookeeper* is selected by default as service registry look up.
-7. qos ports activation is not selected by default but if it is, it can be accessed by port *22222*.
-8. Click *Generate Project* to download the generated project.
-
-This example shows how to generate a server. Similarly, it can generate a *client* by selecting client on the generation interface.
-
-### Run
-
-Open the generated project with an IDE and to see the application is a typical Spring Boot application with the following program entry:
-
-```java
-@SpringBootApplication
-public class DemoApplication {
- public static void main(String[] args) {
- new EmbeddedZooKeeper(2181, false).start(); // #1
- SpringApplication.run(DemoApplication.class, args); // #2
- }
-}
-```
-
-**Notes**：
-
-1. Launch embedded *ZooKeeper* on port *2181*.
-2. Launch the context of *Spring Boot*.
-
-
-Run it directly in IDE and here are the results:
-
-```bash
-2018-05-28 16:59:38.072 INFO 59943 --- [ main] a.b.d.c.e.WelcomeLogoApplicationListener :
-
- ████████▄ ███ █▄ ▀█████████▄ ▀█████████▄ ▄██████▄
- ███ ▀███ ███ ███ ███ ███ ███ ███ ███ ███
- ███ ███ ███ ███ ███ ███ ███ ███ ███ ███
- ███ ███ ███ ███ ▄███▄▄▄██▀ ▄███▄▄▄██▀ ███ ███
- ███ ███ ███ ███ ▀▀███▀▀▀██▄ ▀▀███▀▀▀██▄ ███ ███
- ███ ███ ███ ███ ███ ██▄ ███ ██▄ ███ ███
- ███ ▄███ ███ ███ ███ ███ ███ ███ ███ ███
- ████████▀ ████████▀ ▄█████████▀ ▄█████████▀ ▀██████▀
-
-
- :: Dubbo Spring Boot (v0.1.0) : https://github.com/dubbo/dubbo-spring-boot-project
- :: Dubbo (v2.0.1) : https://github.com/alibaba/dubbo
- :: Google group : http://groups.google.com/group/dubbo
-
-2018-05-28 16:59:38.079 INFO 59943 --- [ main] e.OverrideDubboConfigApplicationListener : Dubbo Config was overridden by externalized configuration {dubbo.application.name=dubbo-demo-server, dubbo.application.qosAcceptForeignIp=false, dubbo.application.qosEnable=true, dubbo.application.qosPort=22222, dubbo.registry.address=zookeeper://localhost:2181?client=curator, dubbo.registry.id=my-registry, dubbo.scan.basePackages=com.example} #1
-
-...
-
-2018-05-28 16:59:39.624 INFO 59943 --- [ main] com.example.demo.DemoApplication : Started DemoApplication in 1.746 seconds (JVM running for 2.963)
-```
-
-**Notes**：
-
-1. In the printouts, the configuration starting with `dubbo.` Is defined in *main/resources/application.properties*.
-
-### Manage service by Telnet
-
-If *qos* is activated during generation, the service can be watched and managed by *telnet* or *nc*.
-
-```bash
-$ telnet localhost 22222
-Trying 127.0.0.1...
-Connected to localhost.
-Escape character is '^]'.
- ████████▄ ███ █▄ ▀█████████▄ ▀█████████▄ ▄██████▄
- ███ ▀███ ███ ███ ███ ███ ███ ███ ███ ███
- ███ ███ ███ ███ ███ ███ ███ ███ ███ ███
- ███ ███ ███ ███ ▄███▄▄▄██▀ ▄███▄▄▄██▀ ███ ███
- ███ ███ ███ ███ ▀▀███▀▀▀██▄ ▀▀███▀▀▀██▄ ███ ███
- ███ ███ ███ ███ ███ ██▄ ███ ██▄ ███ ███
- ███ ▄███ ███ ███ ███ ███ ███ ███ ███ ███
- ████████▀ ████████▀ ▄█████████▀ ▄█████████▀ ▀██████▀
-
-
-dubbo>
-dubbo>ls
-As Provider side:
-+------------------------------+---+
-| Provider Service Name |PUB|
-+------------------------------+---+
-|com.example.HelloService:1.0.0| Y |
-+------------------------------+---+
-As Consumer side:
-+---------------------+---+
-|Consumer Service Name|NUM|
-+---------------------+---+
-```
-
-Currently, *qos* supports following command lines. For more information please refer to the official document. [^4]:
-
-* *ls*：List the information of client and server.
-* *online*：Bring the service online.
-* *offline*：Bring the service offline.
-* *help*：View online help.
-
-## Summary
-
-In this tutorial, we start with RMI and introduce the basic concepts in Java distributed invocations. Based on interface programming, it disguises remote calls as local by agency and run the service registry and looking up by registry center.
-
-Then for simplicity, we introduce how to develop a complete Dubbo demo in an easy way of assembled registry and direct Dubbo API oriented programming. Additionally, we look into the usage of *ServiceConfig* and *RefenceConfig*, which is of great help for further using Spring XML configuration and the programming pattern of Spring Boot.
-
-Eventually, we give an outline of how to create a Dubbo application quickly based on Spring Boot using the public resources, start.dubbo.io, provided by the Dubbo development team and operate and maintain the Dubbo service by *qos*.
-
----
-
-1. [Getting Started Using JavaTM RMI](https://docs.oracle.com/javase/6/docs/technotes/guides/rmi/hello/hello-world.html)
-2. [Explicit target](http://dubbo.apache.org/en-us/docs/user/demos/explicit-target.html)
-3. [Multicast Registry](http://dubbo.apache.org/en-us/docs/user/references/registry/multicast.html)
-4. [Online QOS command](http://dubbo.apache.org/en-us/docs/user/references/qos.html)
diff --git a/blog/en-us/dubbo-annotation.md b/blog/en-us/dubbo-annotation.md
deleted file mode 100644
index 6e90411..0000000
--- a/blog/en-us/dubbo-annotation.md
+++ /dev/null
@@ -1,362 +0,0 @@
----
-title: Use Annotations In Dubbo
-keywords: Dubbo, Annotation, Spring
-description: This article will introduce you how to use annotations instead of XML to develop Dubbo applications, such as `@EnableDubbo`, `@Service` and `@Reference`.
----
-
-# Use Annotations In Dubbo
-
-With the widely promotion and implementation of Microservices Architecture, the Microservices Architecture represented by Spring Boot and Spring Cloud, in Java ecosystem, introduced some brand new programming model, like:
- - Annotation-Driven
- - External Configuration
- - Auto-Configure
-
-New programming model have some advantages, for example, it does not require `XML` configuration, it can simplify deployment process, beyond that，it can promote development efficiency. In order to implement the microservice architecture better，Dubbo has provided more perfect support for the above three scenarios since version 2.5.8. This article focuses on introduce annotations rather than discuss the traditional XML configuration approach. There are two kinds of automatic assembly, exte [...]
-
-
-## Introduce Annotations
-
-### @EnableDubbo
-The annotations of `@EnableDubbo` is a combination of both `@EnableDubboConfig` and `@DubboComponentScan`.Related to the annotation driver is `@DubboComponentScan`.
-
-```java
-package org.apache.dubbo.config.spring.context.annotation;
-
-@EnableDubboConfig
-@DubboComponentScan
-public @interface EnableDubbo {
- /**
- * Base packages to scan for annotated @Service classes.
- * <p>
- * Use {@link #scanBasePackageClasses()} for a type-safe alternative to String-based
- * package names.
- *
- * @return the base packages to scan
- * @see DubboComponentScan#basePackages()
- */
- @AliasFor(annotation = DubboComponentScan.class, attribute = "basePackages")
- String[] scanBasePackages() default {};
-
- /**
- * Type-safe alternative to {@link #scanBasePackages()} for specifying the packages to
- * scan for annotated @Service classes. The package of each class specified will be
- * scanned.
- *
- * @return classes from the base packages to scan
- * @see DubboComponentScan#basePackageClasses
- */
- @AliasFor(annotation = DubboComponentScan.class, attribute = "basePackageClasses")
- Class<?>[] scanBasePackageClasses() default {};
-}
-```
-
-The `@bableDubbo` can be used to scan Dubbo's service provider (marked by `@Service`) and Dubbo's service consumer (marked by `Reference`) under the specified package name (via `scanBasePackages`) or in the specified class (via `scanBasePackageClasses`). After Dubbo's service providers and consumers have been scanned, they have been assembled corresponding and been initialized, and finally the service is exposed or referenced, if you do not use `External Configuration`, you can use `@Du [...]
-
-### @Service
-
-`@service` is used to configure Dubbo's Service provider,for example:
-
-```java
-@Service
-public class AnnotatedGreetingService implements GreetingService {
- public String sayHello(String name) {
- return "hello, " + name;
- }
-}
-```
-
-Via `@Service`'s properties, you can customize Dubbo's Service provider:
-
-```java
-package org.apache.dubbo.config.annotation;
-
-@Documented
-@Retention(RetentionPolicy.RUNTIME)
-@Target({ElementType.TYPE}) // #1
-@Inherited
-public @interface Service {
- Class<?> interfaceClass() default void.class; // #2
- String interfaceName() default ""; // #3
- String version() default ""; // #4
- String group() default ""; // #5
- boolean export() default true; // #6
- boolean register() default true; // #7
-
- String application() default ""; // #8
- String module() default ""; // #9
- String provider() default ""; // #10
- String[] protocol() default {}; // #11
- String monitor() default ""; // #12
- String[] registry() default {}; // #13
-}
-```
-
-Which is more important:
-1. **@Service**: Can only be defined on a class, represent a service
-2. **interfaceClass**: specified `interface`'s class implemented by the service provider
-3. **interfaceName**: specified `interface`'s class name implemented by the service provider
-4. **version**: specified the version number of the service
-5. **group**:specified the group of services
-6. **export**:whether to expose service
-7. **registry**:Whether to register service to the registry
-8. **application**:application configuration
-9. **module**:module configuration
-10. **provider**:service provider configuration
-11. **protocol**:protocol configuration
-12. **monitor**:monitoring center configuration
-13. **registr**:registry configuration
-
-In addition, it should be noted that, `application`, `module`, `provider`, `protocol`, `monitor`, `registry` (from 8 to 13) need to provide the name of the corresponding `spring bean`,These bean assembly completed either through traditional XML configuration,or by the modern Java Config. This article will show you how to use `Java Config`.
-
-### @Reference
-
-`@Reference` is used to configure Dubbo's Service consumer,for example:
-
-```Java
-@Component
-public class GreetingServiceConsumer {
- @Reference
- private GreetingService greetingService;
-
- public String doSayHello(String name) {
- return greetingService.sayHello(name);
- }
-}
-```
-
-Via `@Reference`'s properties, you can customize Dubbo's Service consumer:
-
-```Java
-package org.apache.dubbo.config.annotation;
-
-@Documented
-@Retention(RetentionPolicy.RUNTIME)
-@Target({ElementType.FIELD, ElementType.METHOD, ElementType.ANNOTATION_TYPE}) // #1
-public @interface Reference {
- Class<?> interfaceClass() default void.class; // #2
- String interfaceName() default ""; // #3
- String version() default ""; // #4
- String group() default ""; // #5
- String url() default ""; // #6
-
- String application() default ""; // #7
- String module() default ""; // #8
- String consumer() default ""; // #9
- String protocol() default ""; // #10
- String monitor() default ""; // #11
- String[] registry() default {}; // #12
-}
-```
-
-Which is more important:
-
-1. **@Reference**:you can define it on a field in a class, you can define it on a method, you can even modify another annotation, it represent a reference to a service.Normally `@Reference` is defined in one field
-2. **interfaceClass** : specified `interface`'s class implemented by the service provider
-3. **interfaceName**: specified `interface`'s class name implemented by the service provider
-4. **version**: specified the version number of the service
-5. **group**:pecified the group of services
-6. **url**: invoking the registry directly by specifying the URL of the service provider
-7. **application**:application configuration
-8. **module**:module configuration
-9. **consumer**:service consumer configuration
-10. **protocol**:protocol configuration
-11. **monitor**:monitoring center configuration
-12. **registr**:registry configuration
-
-In addition, it should be noted that, `application`, `module`, `consumer`, `protocol`, `monitor`, `registry` (from 7 to 12) need to provide the name of the corresponding `spring bean`,These bean assembly completed either through traditional XML configuration,or by the modern Java Config. This article will show you how to use `Java Config`.
-
-## Example practice
-
-After learn what `@EnableDubbo`, `@Service`, `@Reference` is, there is a practical example showing how to use the annotation to develop a Dubbo application.The following code can be found at https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-annotation
-
-### 1.Interface Definition
-
-Define a simple `GreetingService` interface with only a simple method `sayHello` to the caller.
-```Java
-public interface GreetingService {
- String sayHello(String name);
-}
-```
-
-### 2.Server:Service Implementation
-
-Implement the `GreetingService` interface, and mark it as a service for Dubbo via @Service.
-
-```Java
-@Service
-public class AnnotatedGreetingService implements GreetingService {
- public String sayHello(String name) {
- return "hello, " + name;
- }
-}
-```
-
-### 3.Server:Assembly Service Provider
-
-You can discover, assemble, and provide Dubbo's services through the Java config technology (@Configuration) and annotation scan (@EnableDubbo) in Spring.
-
-```Java
-@Configuration
-@EnableDubbo(scanBasePackages = "com.alibaba.dubbo.samples.impl")
-static class ProviderConfiguration {
- @Bean // #1
- public ProviderConfig providerConfig() {
- ProviderConfig providerConfig = new ProviderConfig();
- providerConfig.setTimeout(1000);
- return providerConfig;
- }
-
- @Bean // #2
- public ApplicationConfig applicationConfig() {
- ApplicationConfig applicationConfig = new ApplicationConfig();
- applicationConfig.setName("dubbo-annotation-provider");
- return applicationConfig;
- }
-
- @Bean // #3
- public RegistryConfig registryConfig() {
- RegistryConfig registryConfig = new RegistryConfig();
- registryConfig.setProtocol("zookeeper");
- registryConfig.setAddress("localhost");
- registryConfig.setPort(2181);
- return registryConfig;
- }
-
- @Bean // #4
- public ProtocolConfig protocolConfig() {
- ProtocolConfig protocolConfig = new ProtocolConfig();
- protocolConfig.setName("dubbo");
- protocolConfig.setPort(20880);
- return protocolConfig;
- }
-}
-```
-
-Description：
- - Scan all classes marked with `@Service` under `com.alibaba.dubbo.samples.impl` with `@EnableDubbo`
- - Via @Configuration, all @Beans in the ProviderConfiguration are assembled using the way of `Java Config` and then injected into the Dubbo service, which means the class marked with `@Service`.Which included:
-i. **ProviderConfig**:Service provider configuration
-ii. **ApplicationConfig**:Application configuration
-iii.**RegistryConfig**:registry configuration
-iv. **ProtocolConfig**:Protocol configuration
-
- ### 4.Server:Start Service
-
-In the `main` method to provide external `Dubbo` service by starting a `Spring Context`.
-
-```Java
-public class ProviderBootstrap {
- public static void main(String[] args) throws Exception {
- new EmbeddedZooKeeper(2181, false).start(); // #1
- AnnotationConfigApplicationContext context = new AnnotationConfigApplicationContext(ProviderConfiguration.class); // #2
- context.start(); // #3
- System.in.read(); // #4
- }
-}
-```
-
-Description：
-1. Start an embedded `zookeeper` and provide service registry on port `2181`
-2. Initialize an example of an AnnotationConfigApplicationContext and pass the `ProviderConfiguration` into the example to complete the automatic discovery and assembly of the `Dubbo` service.
-3. Start the `Spring Context` and start providing external `Dubbo` services.
-4. Because it is a server, you need to prevent the process exit by blocking the main thread.
-
-Start the `main` method of the server, you will see the following output, on behalf of the server startup success, and registered the `GreetingService` service in the `ZookeeperRegistry`:
-```sh
-[01/08/18 02:12:51:051 CST] main INFO transport.AbstractServer: [DUBBO] Start NettyServer bind /0.0.0.0:20880, export /192.168.99.1:20880, dubbo version: 2.6.2, current host: 192.168.99.1
-
-[01/08/18 02:12:51:051 CST] main INFO zookeeper.ZookeeperRegistry: [DUBBO] Register: dubbo://192.168.99.1:20880/com.alibaba.dubbo.samples.api.GreetingService?anyhost=true&application=dubbo-annotation-provider&default.timeout=1000&dubbo=2.6.2&generic=false&interface=com.alibaba.dubbo.samples.api
-```
-
-### 5.Server:Reference Service
-
-Marking the member variable of the `GreetingService` via `@Reference` .The `greetingService` is a reference to the `Dubbo` service, which means that it can simply provide through the interface to the remote party to initiate service calls, and the client does not implement `GreetingService` interface.
-
-```Java
-@Component("annotatedConsumer")
-public class GreetingServiceConsumer {
- @Reference
- private GreetingService greetingService;
-
- public String doSayHello(String name) {
- return greetingService.sayHello(name);
- }
-}
-```
-
-### 6.Server:Assembly Service consumer
-
-Just like **3. Server:Assembly Service Provider** You can discover, assemble, and provide Dubbo's service consumer through the Java config technology (@Configuration) and annotation scan (@EnableDubbo) in Spring.
-
-```Java
-@Configuration
-@EnableDubbo(scanBasePackages = "com.alibaba.dubbo.samples.action")
-@ComponentScan(value = {"com.alibaba.dubbo.samples.action"})
-static class ConsumerConfiguration {
- @Bean // #1
- public ApplicationConfig applicationConfig() {
- ApplicationConfig applicationConfig = new ApplicationConfig();
- applicationConfig.setName("dubbo-annotation-consumer");
- return applicationConfig;
- }
-
- @Bean // #2
- public ConsumerConfig consumerConfig() {
- ConsumerConfig consumerConfig = new ConsumerConfig();
- consumerConfig.setTimeout(3000);
- return consumerConfig;
- }
-
- @Bean // #3
- public RegistryConfig registryConfig() {
- RegistryConfig registryConfig = new RegistryConfig();
- registryConfig.setProtocol("zookeeper");
- registryConfig.setAddress("localhost");
- registryConfig.setPort(2181);
- return registryConfig;
- }
-}
-```
-
-Description：
- - Scan all classes marked with `@Service` under `com.alibaba.dubbo.samples.impl` with `@Reference`
- - Via @Configuration, all @Beans in the ProviderConfiguration are assembled using the way of `Java Config` and then injected into the Dubbo service, which means the class marked with `@Reference`.Which included:
-i. `ApplicationConfig`: Application configuration
-ii. `ConsumerConfig`:Service consumer configuration
-iii.`RegistryConfig`:Registry configuration.Note:The configuration here needs to be consistent with the configuration information of the EmbeddedZooKeeper when started by the service provider.
-
-### 7.Server: Initiate Remote Calls
-
-In the `main` method, you can start a `Spring Context` to find the service consumer of the assembled `Dubbo` from it, and initiate a remote call.
-
-```Java
-public class ConsumerBootstrap {
- public static void main(String[] args) {
- AnnotationConfigApplicationContext context = new AnnotationConfigApplicationContext(ConsumerConfiguration.class); // #1
- context.start(); // #2
- GreetingServiceConsumer greetingServiceConsumer = context.getBean(GreetingServiceConsumer.class); // #3
- String hello = greetingServiceConsumer.doSayHello("annotation"); // #4
- System.out.println("result: " + hello); // #5
- }
-}
-```
-
-Description：
- - Initialize an example of an AnnotationConfigApplicationContext and pass the `ProviderConfiguration` into the example to complete the automatic discovery and assembly of the `Dubbo` service consumer.
- - start `Spring Context`.
- - Find `bean` which type is `GreetingServiceConsumer` from `Context`.
- - Call the `doSayHello` method and finally initiate a remote call via Dubbo's service reference (marked by @Reference)
- - Print call result
-Start the Server's `main` method, you will see the following output, which returns the `result`: hello, annotation:
-
-```sh
-[01/08/18 02:38:40:040 CST] main INFO config.AbstractConfig: [DUBBO] Refer dubbo service com.alibaba.dubbo.samples.api.GreetingService from url zookeeper://localhost:2181/com.alibaba.dubbo.registry.RegistryService?anyhost=true&application=dubbo-annotation-consumer&check=false&default.timeout=3000&dubbo=2.6.2&generic=false&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=33001®ister.ip=192.168.99.1&remote.timestamp=1533105502086&side=consumer×tamp=153 [...]
-[01/08/18 02:38:40:040 CST] main INFO annotation.ReferenceBeanBuilder: <dubbo:reference object="com.alibaba.dubbo.common.bytecode.proxy0@673be18f" singleton="true" interface="com.alibaba.dubbo.samples.api.GreetingService" uniqueServiceName="com.alibaba.dubbo.samples.api.GreetingService" generic="false" id="com.alibaba.dubbo.samples.api.GreetingService" /> has been built.
-result: hello, annotation
-```
-
-## Conclusion
-
-By studying this article, the reader can master the basic concepts of `Dubbo`'s exclusive `annotations` , `@EnableDubbo`, `@Service`, `@Reference`, and master it's basic usage through a simple `Dubbo` application.
-
-In addition to traditional `XML` configuration, `Spring` offers more modern configurations such as annotation drivers, externalization, and auto-assembly.This article focuses on the development of `Dubbo` applications through annotations. You can be seen that annotation mode programming is more concise and simple than XML configuration. In future, we will introduce the use of externalization configuration and automatic assembly in `Dubbo` further.
diff --git a/blog/en-us/dubbo-basic-usage-dubbo-consumer-configuration.md b/blog/en-us/dubbo-basic-usage-dubbo-consumer-configuration.md
deleted file mode 100644
index 4a31905..0000000
--- a/blog/en-us/dubbo-basic-usage-dubbo-consumer-configuration.md
+++ /dev/null
@@ -1,193 +0,0 @@
-# DubboBasic Usage - Dubbo Consumer Configuration
-
-## Dubbo Consumer Configuration
-
-### Consumer Configuration Detailed
-
-There are 3 ways to configure the Dubbo Consumer: XML configuration, API call mode configuration, and annotation mode configuration.
-
-#### XML Configuration
-
-###### Example of the simplest configuration:
-
-```
-
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- Xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- Xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- Xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema /dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
- <dubbo:application name="hello-world-app" />
- <dubbo:registry address="multicast://224.5.6.7:1234" />
- <dubbo:protocol name="dubbo" port="20880" />
- <dubbo:reference id="demoServiceRemote" interface="com.alibaba.dubbo.demo.DemoService" />
-</beans>
-```
-
-
-
-> For the supported configuration tags and corresponding configuration items, refer to the usage in the provider.
-
-> Next, focus on the configuration of <dubbo:reference/>.
-
-
-
-* <dubbo:reference/> List of main attributes supported:
-
-| Property Name | Description |
-| -------- | ----- |
-| id | service reference id, as java bean id, requires unique |
-Interface | interface name for finding services |
-| version | version number, consistent with the service provider's version |
-| timeout | service method call timeout (ms) |
-| retries | The number of retry attempts by the remote service, excluding the first call, no need to retry, please set to 0 |
-Connections | For each provider's maximum number of connections, rmi, http, hessian, etc. The short connection protocol indicates the number of restricted connections, and the dubbo equal-length connection association indicates the number of long connections established |
-Loadbalance | Load balancing policy, optional values: random, roundrobin, leastactive, respectively: random, polling, least active call |
-| async | Whether to execute asynchronously, unreliable asynchronous, just ignore return value, do not block execution thread |
-| generic | generalized call, can bypass |
-| check | Check if the provider exists at startup, true error, false ignore |
-Actives | Maximum concurrent calls per method per service consumer |
-
-
-
-For other configuration properties, please refer to xsd: http://dubbo.apache.org/schema/dubbo/dubbo.xsd
-
-
-
-* <dubbo:method/> As a child of <dubbo:reference/>, it can be configured for methods. The more commonly used attributes are:
-
-
-
-| Property Name | Description |
-| -------- | ----- |
-| executes | request ceiling for service execution |
-| retries | Timeout retries |
-| timeout | call timeout |
-Loadbalance | Load balancing policy, optional values: random, roundrobin, leastactive, respectively: random, polling, least active call |
-| async | Whether to execute asynchronously, unreliable asynchronous, just ignore return value, do not block execution thread |
-Actives | Maximum concurrent call limit per service consumer |
-
-For other properties, you can refer to xsd above.
-
-###### Configured coverage relationship
-
-
-
-Coverage diagram for <center> configuration</center>
-
-It contains the configuration of the consumer side and the provider, pay attention to the distinction.
-
-#### annotation
-
-
-###### Reference Annotation Remote Service
-
-```
-
-Public class AnnotationConsumeService {
-
- @com.alibaba.dubbo.config.annotation.Reference
- Public AnnotateService annotateService;
-
- // ...
-
-}
-
-```
-
-
-
-The configuration in this way is the same as the previous configuration in xml.
-
-
-
-> To specify the way dubbo scans the path, refer to the implementation of the provider in the previous section.
-
-
-
-
-
-#### api direct trigger
-
-```
-Import com.alibaba.dubbo.rpc.config.ApplicationConfig;
-Import com.alibaba.dubbo.rpc.config.RegistryConfig;
-Import com.alibaba.dubbo.rpc.config.ConsumerConfig;
-Import com.alibaba.dubbo.rpc.config.ReferenceConfig;
-Import com.xxx.XxxService;
-// current application configuration
-
-ApplicationConfig application = new ApplicationConfig();
-application.setName("yyy");
-// Connect to the registry configuration
-RegistryConfig registry = new RegistryConfig();
-registry.setAddress("10.20.130.230:9090");
-registry.setUsername("aaa");
-registry.setPassword("bbb");
-
-// Note: ReferenceConfig is a heavy object that internally encapsulates the connection to the registry and the connection to the service provider.
-// reference remote service
-ReferenceConfig<XxxService> reference = new ReferenceConfig<XxxService>(); // This instance is heavy, encapsulates the connection to the registry and the connection to the provider, please cache it yourself, otherwise it may cause memory and connection leaks.
-
-reference.setApplication(application);
-reference.setRegistry(registry); // Multiple registries can use setRegistries()
-reference.setInterface(XxxService.class);
-reference.setVersion("1.0.0");
-
-// Use xxxService like local beans
-XxxService xxxService = reference.get();
-```
-
-###### methodSpecial settings
-
-```
-
-// Method level configuration
-List<MethodConfig> methods = new ArrayList<MethodConfig>();
-MethodConfig method = new MethodConfig();
-method.setName("createXxx");
-method.setTimeout(10000);
-method.setRetries(0);
-Methods.add(method);
-// reference remote service
-ReferenceConfig<XxxService> reference = new ReferenceConfig<XxxService>(); // This instance is heavy, encapsulates the connection to the registry and the connection to the provider, please cache it yourself, otherwise it may cause memory and connection leaks.
-...
-reference.setMethods(methods); // Set method level configuration
-```
-
-### Consumer Calling Remote Service
-The above chapters are more from a configuration point of view, and then through a complete example, explain the complete use of dubbo consumer.
-
-There is only one service UserReadService in this example, there is a method getUserById. Need to call a remote service through Dubbo. The specific steps are as follows:
-
-1. Create a project
-If there is already a project, you can ignore it. Create a spring boot project that can be created at https://start.spring.io/.
-The provider of the service has been defined in the provider section.
-2. Call the service
-```
-@RestController
-Public class UserTestController{
- @Autowired
- Private UserReadService userReadService;
- @RequestMapping("/user/getById")
- Public String getUserById(Long id){
- // just test
- Return userReadService.getUserById(id).toString();
- }
-}
-```
-3.Dubbo configuration
-```
-
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- Xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- Xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- Xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema /dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
- <dubbo:application name="hello-world-app" />
- <dubbo:registry address="multicast://224.5.6.7:1234" />
- <dubbo:protocol name="dubbo" port="20880" />
- <dubbo:reference id="userReadService" interface="com.package.UserReadService"check="false" />
-</beans>
-```
-Other ways of configuring Dubbo can refer to the relevant configuration in the previous section, or use the integrated dubbo spring boot starter mode.
\ No newline at end of file
diff --git a/blog/en-us/dubbo-basic-usage-dubbo-provider-configuration.md b/blog/en-us/dubbo-basic-usage-dubbo-provider-configuration.md
deleted file mode 100644
index f674e08..0000000
--- a/blog/en-us/dubbo-basic-usage-dubbo-provider-configuration.md
+++ /dev/null
@@ -1,288 +0,0 @@
----
-title: Dubbo Basic Usage -- Dubbo Provider Configuration
-keywords: Dubbo, Provider, Configuration
-description: This article will introduce you how to config Dubbo, by XML, property files, annotations or Java code.
----
-
-Dubbo Basic Usage -- Dubbo Provider Configuration
----
-
-# Dubbo Basic Usage
-
-This chapter mainly talking about how to configure dubbo. According to the configuration mode, it can be divided into the following mode: XML Configuration, Properties Configuration, Annotation Configuration, API Invocation Mode Configuration. And according to the function, we can divide them into Dubbo Provider and Dubbo Consumer. In the following sections, we would explain Dubbo Provider and Dubbo Consumer respectively.
-
-## Dubbo Provider Configuration
-
-### Provider Configuration in Detail
-
-The configuration mode of Dubbo Provider has 4 different ways: XML Configuration, Properties Configuration, API Invocation Mode Configuration and Annotation Configuration.
-
-#### XML Configuration
-
-###### The simplest configuration example：
-```
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
- <dubbo:application name="hello-world-app" />
- <dubbo:registry address="multicast://224.5.6.7:1234" />
- <dubbo:protocol name="dubbo" port="20880" />
- <dubbo:service interface="com.alibaba.dubbo.demo.DemoService" ref="demoServiceLocal" />
- <dubbo:reference id="demoServiceRemote" interface="com.alibaba.dubbo.demo.DemoService" />
-</beans>
-```
-In the example above，note the way to write dubbo schema：
-```
-<beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://code.alibabatech.com/schema/dubbo"
- xmlns="http://www.springframework.org/schema/beans"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd
- http://code.alibabatech.com/schema/dubbo http://code.alibabatech.com/schema/dubbo/dubbo.xsd">
-```
-
-###### Supported Configuration Tags
-
-| Tags | Application | Describe |
-| -------- | ----- | :---- |
-| <dubbo:service/> | Service Configuration | Expose a service, define the meta information of the service. One service can use multiple protocols to expose and can be registered to multiple registry centers |
-| <dubbo:reference/> | Reference Configuration | Create a remote service agent, one reference can point to multiple registry centers |
-| <dubbo:protocol/> | Protocol Configuration | Configure protocol information for providing services, protocol is specified by the provider and accepted passively by the consumer |
-| <dubbo:application/> | Application Configuration | Configure current application information, regardless of whether the application is provider or consumer |
-| <dubbo:module/> | Module Configuration | Configure current module information. Optional |
-| <dubbo:registry/> | Registry Center Configuration | Configure information related to connect registry centers |
-| <dubbo:monitor/> | Monitoring Center Configuration | Configure information related to connect monitor centers. Optional |
-| <dubbo:provider/> | Provider Configuration | When some properties ProtocolConfig or ServiceConfig are not configured, use this default value. Optional |
-| <dubbo:consumer/> | Consumer Configuration | When some properties of ReferenceConfig are not configured, use this default value. Optional |
-| <dubbo:method/> | Method Configuration | Configure specific method level information of ServiceConfig and ReferenceConfig |
-| <dubbo:argument/> | Parameter Configuration | Configure parameters of specific method |
-
-
-
- <center>Configuration Diagram</center>
-
-###### Configuration item in detail
-
-* <dubbo:application name="hello-world-app" />
-Apply to specific application name, note that you need to make sure that the application name is unique. The application name can be displayed in the following console admin for easy management.
-
-* <dubbo:registry address="multicast://224.5.6.7:1234" />
-Configure registry center, related to the specific mechanism of service discovery. It can be zookeeper address or eureka address. The address above is the broadcast address, which is very convenient in the test process of the local service invocation.
-
-* <dubbo:protocol name="dubbo" port="20880" />
-Here is the transport protocol and the default port, generally no changes are required.
-
-> Next, we will focus on the configuration of <dubbo:service/>
-
-* <dubbo:service/>mainly supports the following properties：
-
-| Properties Name | Description |
-| -------- | ----- |
-| version | Version number |
-| scope | Service visibility, value can be local or remote，remote by default |
-| actives | Maximum number of activated requests |
-| async | Whether the method called asynchronously，false by default |
-| cache | Service cache，optional value：lru/threadlocal/jcache |
-| callbacks | Limitation of callback instance |
-| generic | Generalized calls which can be bypassed |
-| class | The implementation of the service's class name |
-| connections | The number of connections in the service |
-| delay | The number of milliseconds delay for publicating the service |
-| executes | Upper bound of service execution requests |
-| retries | Timeout retry times |
-| timeout | Invocation timeout time |
-
-For other configuration properties, please refer to xsd：http://dubbo.apache.org/schema/dubbo/dubbo.xsd
-
-* <dubbo:method/> as the sub-element of <dubbo:service/> can be configured corresponding to method. Properties that are commonly used are：
-
-| Properties Name | Description |
-| -------- | ----- |
-| executes | Upper bound of service execution requests |
-| retries | Timeout retry times |
-| timeout | Invocation timeout time |
-
-For other properties，you can refer to xsd above。
-
-###### Configuration Override Relationship
-
-
-<center>Configuration Coverage Relationship Diagram</center>
-
-The Override relationship here includes the configuration of both provider end and consumer end. If you have any questions about consumer, you can refer to the next chapter, consumer chapter, to understand.
-
-#### dubbo.properties Configuration
-
-> If the public configuration is very simple, no multiple registry centers, no multiple protocols, etc., or if you want multiple Spring containers to share the configuration, you can use dubbo.properties as the default configurations.
-
-Dubbo would load dubbo.properties under the classpath root directory automaticaly，you can change the default configuration location by JVM startup parameter -Ddubbo.properties.file=xxx.properties.
-
-###### dubbo.properties Configuration example
-```
-# application name
-dubbo.application.name=dubbodemo-provider
-# registry center address
-dubbo.registry.address=zookeeper://localhost:2181
-# Example of broadcasting registry center
-#dubbo.registry.address=multicast://224.5.6.7:1234
-# address for calling protocol
-dubbo.protocol.name=dubbo
-dubbo.protocol.port=28080
-```
-
-
-###### Mapping Rule
-Split the tag name and properties in XML configuration with dots, and multiple properties should be split into multiple lines
-* For example: dubbo.application.name=foo equivalents to <dubbo:application name="foo" />
-* For example: dubbo.registry.address=10.20.153.10:9090 equivalents to <dubbo:registry address="10.20.153.10:9090" />
-
-If there are multiple configurations having the same tag name, they can be distinguished by id, and if there is no id, the configurations will be applied to all tags with the same name.
-* For example: dubbo.protocol.rmi.port=1234 equivalents to <dubbo:protocol id="rmi" name="rmi" port="1234" />
-* For example: dubbo.registry.china.address=10.20.153.10:9090 equivalents to <dubbo:registry id="china" address="10.20.153.10:9090" />
-
-###### Coverage Strategy
-
-
-* When JVM starts, -D parameter has priority, so that users can rewrite the parameters when deploy and start, for example, the protocol port should be changed when start.
-* Then comes to XML, the configurations in dubbo.properties are invalid, if they are configured in XML.
-* Properties are the last, which can be considered as default value. Only when there is no configuration in XML, the corresponding configuarations in dubbo.properties will become effective, which usually applies to shared public configuration, like application name.
-
-> Note:
-1. If there are multiple dubbo.properties in the classpath root directory, for example, if dubbo.properties exist in multiple JAR files, Dubbo will load anyone arbitrarily and print the Error logs, which may change to throwing exceptions later.↩
-2. When the protocol's id is not configured, protocol name will be used as id as default.
-
-#### Annotation
-
-###### Service Annotation Exposure Service
-```
-import com.alibaba.dubbo.config.annotation.Service;
-
-@Service(timeout = 5000)
-public class AnnotateServiceImpl implements AnnotateService {
- // ...
-}
-```
-###### Javaconfig Configuration Public Module
-```
-@Configuration
-public class DubboConfiguration {
-
- @Bean
- public ApplicationConfig applicationConfig() {
- ApplicationConfig applicationConfig = new ApplicationConfig();
- applicationConfig.setName("provider-test");
- return applicationConfig;
- }
-
- @Bean
- public RegistryConfig registryConfig() {
- RegistryConfig registryConfig = new RegistryConfig();
- registryConfig.setAddress("zookeeper://127.0.0.1:2181");
- registryConfig.setClient("curator");
- return registryConfig;
- }
-}
-```
-
-The result of configuration using this method is the same as that of using xml.
-
-###### Specify the Dubbo Scan Path
-```
-@SpringBootApplication
-@DubboComponentScan(basePackages = "com.alibaba.dubbo.test.service.impl")
-public class ProviderTestApp {
- // ...
-}
-```
-or use the spring bean xml configuration:
-```
-<dubbo:annotation package="com.chanshuyi.service.impl" />
-```
-
-#### API Trigger Directly
-```
-import com.alibaba.dubbo.rpc.config.ApplicationConfig;
-import com.alibaba.dubbo.rpc.config.RegistryConfig;
-import com.alibaba.dubbo.rpc.config.ProviderConfig;
-import com.alibaba.dubbo.rpc.config.ServiceConfig;
-import com.xxx.XxxService;
-import com.xxx.XxxServiceImpl;
-
-// Service implementation
-XxxService xxxService = new XxxServiceImpl();
-
-// current application configuration
-ApplicationConfig application = new ApplicationConfig();
-application.setName("xxx");
-
-// connect to registry center configuration
-RegistryConfig registry = new RegistryConfig();
-registry.setAddress("10.20.130.230:9090");
-registry.setUsername("aaa");
-registry.setPassword("bbb");
-
-// service provider's protocol configuration
-ProtocolConfig protocol = new ProtocolConfig();
-protocol.setName("dubbo");
-protocol.setPort(12345);
-protocol.setThreads(200);
-
-// Note: ServiceConfig is a heavy object, which encapsulated the connection with registry center internally, and open the service port
-
-// Service provider exposes service configuration
-ServiceConfig<XxxService> service = new ServiceConfig<XxxService>(); // This instance is very heavy, which encapsulated the connection with registry center, please cache it by yourself, it might cause memory and connection leakage otherwise.
-service.setApplication(application);
-service.setRegistry(registry); // multiple registry centers can use setRegistries()
-service.setProtocol(protocol); // multiple protocols can use setProtocols()
-service.setInterface(XxxService.class);
-service.setRef(xxxService);
-service.setVersion("1.0.0");
-
-// exposure and register service
-service.export();
-```
-
-Generally, this method is not recommended in spring applications. The reason can be checked by reading the source code on github, which would not be explained here.
-
-### Provider Interface and Implement
-The above chapters are described mainly from a configuration perspective, and lets explain the complete use of Dubbo provider by going through a complete example.
-
-There is only one service UserReadService, and one method getUserById in this example.
-This service need to be exposed to a remote service by Dubbo. Detail steps are shown below:
-
-1. Create Project
-Skip this step if there is already a project. Create a Spring Boot project, which can be created through https://start.spring.io/.
-2. Define Interface
-Define interface: UserReadService
-```
-public interface UserReadService{
- public User getUserById(Long userId);
-}
-```
-Generally, this interface should be placed in an independent JAR file as a client package.
-Generally, the other services need to refer this client package if they want to consume this service(except for generalized call).
-3. Implement Interface
-Implement UserReadService, and deploy current implementation in the Provider's application.
-```
-public UserReadServiceImpl implements UserReadService{
- public User getUserById(Long userId){
- return xxx;
- }
-}
-```
-4. Dubbo Configuration
-```
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
- <dubbo:application name="hello-world-app" />
- <dubbo:registry address="multicast://224.5.6.7:1234" />
- <dubbo:protocol name="dubbo" port="20880" />
- <bean id="userReadService" class="com.package.UserReadServiceImpl"/>
- <dubbo:service interface="com.package.UserReadService" ref="userReadService" />
-</beans>
-```
-For the other modes of Dubbo configuration, please refer to the related configurations in the previous chapter, or use the integrated Dubbo Spring Boot starter method.
diff --git a/blog/en-us/dubbo-fescar.md b/blog/en-us/dubbo-fescar.md
deleted file mode 100644
index 75736f8..0000000
--- a/blog/en-us/dubbo-fescar.md
+++ /dev/null
@@ -1,227 +0,0 @@
----
-title: How to use Fescar to ensure consistency between Dubbo Microservices
-keywords: Dubbo,Fescar,Consistency
-description: This article will introduce you how to use Fescar to ensure consistency between Dubbo Microservices.
----
-# How to use Fescar to ensure consistency between Dubbo Microservices
-
-
-
-## Use case
-
-A business logic for user purchasing commodities. The whole business logic is powered by 3 microservices:
-
-- Storage service: deduct storage count on given commodity.
-- Order service: create order according to purchase request.
-- Account service: debit the balance of user's account.
-
-### Architecture
-
-
-
-
-### StorageService
-
-```java
-public interface StorageService {
-
- /**
- * deduct storage count
- */
- void deduct(String commodityCode, int count);
-}
-```
-
-### OrderService
-
-```java
-public interface OrderService {
-
- /**
- * create order
- */
- Order create(String userId, String commodityCode, int orderCount);
-}
-```
-
-### AccountService
-
-```java
-public interface AccountService {
-
- /**
- * debit balance of user's account
- */
- void debit(String userId, int money);
-}
-```
-
-### Main business logic
-
-```java
-public class BusinessServiceImpl implements BusinessService {
-
- private StorageService storageService;
-
- private OrderService orderService;
-
- /**
- * purchase
- */
- public void purchase(String userId, String commodityCode, int orderCount) {
-
- storageService.deduct(commodityCode, orderCount);
-
- orderService.create(userId, commodityCode, orderCount);
- }
-}
-```
-
-```java
-public class StorageServiceImpl implements StorageService {
-
- private StorageDAO storageDAO;
-
- @Override
- public void deduct(String commodityCode, int count) {
- Storage storage = new Storage();
- storage.setCount(count);
- storage.setCommodityCode(commodityCode);
- storageDAO.update(storage);
- }
-}
-```
-
-```java
-public class OrderServiceImpl implements OrderService {
-
- private OrderDAO orderDAO;
-
- private AccountService accountService;
-
- public Order create(String userId, String commodityCode, int orderCount) {
-
- int orderMoney = calculate(commodityCode, orderCount);
-
- accountService.debit(userId, orderMoney);
-
- Order order = new Order();
- order.userId = userId;
- order.commodityCode = commodityCode;
- order.count = orderCount;
- order.money = orderMoney;
-
- return orderDAO.insert(order);
- }
-}
-```
-
-## Distributed Transaction Solution with Fescar
-
-
-
-We just need an annotation `@GlobalTransactional` on business method:
-
-```java
-
- @GlobalTransactional
- public void purchase(String userId, String commodityCode, int orderCount) {
- ......
- }
-```
-
-## Example powered by Dubbo + Fescar
-
-### Step 1: Setup database
-
-- Requirement: MySQL with InnoDB engine.
-
-**Note:** In fact, there should be 3 database for the 3 services in the example use case. However, we can just create one database and configure 3 data sources for simple.
-
-Modify Spring XML with the database URL/username/password you just created.
-
-dubbo-account-service.xml
-dubbo-order-service.xml
-dubbo-storage-service.xml
-
-```xml
- <property name="url" value="jdbc:mysql://x.x.x.x:3306/xxx" />
- <property name="username" value="xxx" />
- <property name="password" value="xxx" />
-```
-### Step 2: Create undo_log table for Fescar
-
-`UNDO_LOG` table is required by Fescar AT mode.
-
-```sql
--- Note that when Fescar version is upgraded to 0.3.0+, it is changed from the previous normal index to the unique index.
-CREATE TABLE `undo_log` (
- `id` bigint(20) NOT NULL AUTO_INCREMENT,
- `branch_id` bigint(20) NOT NULL,
- `xid` varchar(100) NOT NULL,
- `rollback_info` longblob NOT NULL,
- `log_status` int(11) NOT NULL,
- `log_created` datetime NOT NULL,
- `log_modified` datetime NOT NULL,
- `ext` varchar(100) DEFAULT NULL,
- PRIMARY KEY (`id`),
- UNIQUE KEY `ux_undo_log` (`xid`,`branch_id`)
-) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8;
-```
-
-### Step 3: Create tables for example business
-
-```sql
-
-DROP TABLE IF EXISTS `storage_tbl`;
-CREATE TABLE `storage_tbl` (
- `id` int(11) NOT NULL AUTO_INCREMENT,
- `commodity_code` varchar(255) DEFAULT NULL,
- `count` int(11) DEFAULT 0,
- PRIMARY KEY (`id`),
- UNIQUE KEY (`commodity_code`)
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-
-DROP TABLE IF EXISTS `order_tbl`;
-CREATE TABLE `order_tbl` (
- `id` int(11) NOT NULL AUTO_INCREMENT,
- `user_id` varchar(255) DEFAULT NULL,
- `commodity_code` varchar(255) DEFAULT NULL,
- `count` int(11) DEFAULT 0,
- `money` int(11) DEFAULT 0,
- PRIMARY KEY (`id`)
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-
-DROP TABLE IF EXISTS `account_tbl`;
-CREATE TABLE `account_tbl` (
- `id` int(11) NOT NULL AUTO_INCREMENT,
- `user_id` varchar(255) DEFAULT NULL,
- `money` int(11) DEFAULT 0,
- PRIMARY KEY (`id`)
-) ENGINE=InnoDB DEFAULT CHARSET=utf8;
-```
-### Step 4: Start Fescar-Server
-
-- Download server [package](https://github.com/alibaba/fescar/releases), unzip it.
-- Start Fescar-Server
-
-```shell
-sh fescar-server.sh $LISTEN_PORT $PATH_FOR_PERSISTENT_DATA
-
-e.g.
-
-sh fescar-server.sh 8091 /home/admin/fescar/data/
-```
-
-### Step 5: Run example
-
-- Start AccountService ([DubboAccountServiceStarter](https://github.com/fescar-group/fescar-samples/blob/master/dubbo/src/main/java/com/alibaba/fescar/samples/dubbo/starter/DubboAccountServiceStarter.java)).
-- Start StorageService ([DubboStorageServiceStarter](https://github.com/fescar-group/fescar-samples/blob/master/dubbo/src/main/java/com/alibaba/fescar/samples/dubbo/starter/DubboStorageServiceStarter.java)).
-- Start OrderService ([DubboOrderServiceStarter](https://github.com/fescar-group/fescar-samples/blob/master/dubbo/src/main/java/com/alibaba/fescar/samples/dubbo/starter/DubboOrderServiceStarter.java)).
-- Run BusinessService for test ([DubboBusinessTester](https://github.com/fescar-group/fescar-samples/blob/master/dubbo/src/main/java/com/alibaba/fescar/samples/dubbo/starter/DubboBusinessTester.java)).
-
-### Related projects
-* fescar: https://github.com/alibaba/fescar/
-* fescar-samples : https://github.com/fescar-group/fescar-samples
diff --git a/blog/en-us/dubbo-generic-invoke.md b/blog/en-us/dubbo-generic-invoke.md
deleted file mode 100644
index 4377ba1..0000000
--- a/blog/en-us/dubbo-generic-invoke.md
+++ /dev/null
@@ -1,186 +0,0 @@
----
-title: Generic invoke of Dubbo
-keywords: Dubbo, Generic invoke
-description: This article introduces you when and how to use generic invoke of Dubbo.
----
-
-# Generic invoke of Dubbo
-
-The generic invoke could be considered to be used in the following cases:
-
-- Service test platform
-- API service gateway
-
-The generic invoke is mainly used when the consumer does not have an API interface;
-instead of depending the interface jar package, the service call is initiated directly through the GenericService interface, and all POJOs in the parameters and return values are represented by a `Map`.
-Generic invoke does not require attention on the server and can be exposed as normal services.
-
-Next, let's take a look at how the consumer uses generic invoke for service call.
-
-## Generic invoke through Spring XML configuration
-
-Declare `generic="true"` in Spring configuration, such as
-
-```xml
-"userService" interface="com.alibaba.dubbo.samples.generic.api.IUserService" generic="true"/>
-```
-
-Where you need to use it, you can call it by forcing a type cast to GenericService.
-
-```java
-GenericService userService = (GenericService) context.getBean("userService");
-// primary param and return value
-String name = (String) userService.$invoke("delete", new String[]{int.class.getName()}, new Object[]{1});
-System.out.println(name);
-```
-
-Among them,
-
-1. The interface GenericService has only one method, named $invoke, which takes three arguments, a method name, an array of method parameter types, and an array of parameter values.
-
-2. For arrays of method parameter types
-
- i. If it is a basic type, such as int or long, use `int.class.getName()` to get its type;
-
- ii. If it is a basic type array, such as int[], use `int[].class.getName()`;
-
- iii. If it is a POJO, use the full class name directly, such as `com.alibaba.dubbo.samples.generic.api.Params`.
-
-## Generic invoke through API programming
-
-```java
-ApplicationConfig application = new ApplicationConfig()ApplicationConfig application = new ApplicationConfig();
-application.setName("api-generic-consumer");
-
-RegistryConfig registry = new RegistryConfig();
-registry.setAddress("zookeeper://127.0.0.1:2181");
-
-application.setRegistry(registry);
-
-ReferenceConfig<GenericService> reference = new ReferenceConfig<GenericService>();
-// weak type interface name
-reference.setInterface("com.alibaba.dubbo.samples.generic.api.IUserService");
-// declared as a generalized interface
-reference.setGeneric(true);
-
-reference.setApplication(application);
-
-// replace all interface references with com.alibaba.dubbo.rpc.service.GenericService
-GenericService genericService = reference.get();
-
-String name = (String) genericService.$invoke("delete", new String[]{int.class.getName()}, new Object[]{1});
-System.out.println(name);
-```
-
-Through the API, you don't need to configure the service in advance like XML. You can dynamically construct ReferenceConfig; the API is more common than XML.
-
-## The case where parameters or return values are POJOs
-
-For example, the method signature is `User get(Params params)`, where `User` has two attributes, id and name, and `Params` has one attribute, query.
-
-The following is the code of the consumer:
-
-```java
-String[] parameterTypes = new String[]{"com.alibaba.dubbo.samples.generic.api.Params"};
-Map<String, Object> params = new HashMap<String, Object>();
-param.put("class", "com.alibaba.dubbo.samples.generic.api.Params");
-param.put("query", "a=b");
-Object user = userService.$invoke("get", parameterTypes, new Object[]{param});
-System.out.println("sample one result: " + user);
-```
-
-The output of the above code is:
-
-```
-sample one result: {name=charles, id=1, class=com.alibaba.dubbo.samples.generic.api.User}
-```
-
-Here, the Dubbo framework will automatically convert the return value from POJO to Map.
-It can be seen that the return value `user` is a HashMap, which stores three k/vs, name, id, and class.
-
-## Generic interface implementation
-
-The implementation of the generic interface is mainly used when the server does not have an API interface. All POJOs in the parameters and return values are represented by Map, which is usually used for framework integration. For example, to implement a generic remote service Mock framework, all service requests can be handled by implementing the interface GenericService.
-
-### Implementation GenericService on the server
-
-```java
-public class GenericServiceImpl implements GenericService {
- @Override
- public Object $invoke(String method, String[] parameterTypes, Object[] args) throws GenericException {
- if (method.equals("hi")) {
- return "hi, " + args[0];
- } else if (method.equals("hello")) {
- return "hello, " + args[0];
- }
-
- return "welcome";
- }
-}
-```
-
-### Server exposed service
-
-```java
-ApplicationConfig application = new ApplicationConfig();
-application.setName("api-generic-provider");
-
-RegistryConfig registry = new RegistryConfig();
-registry.setAddress("zookeeper://127.0.0.1:2181");
-
-application.setRegistry(registry);
-
-GenericService genericService = new GenericServiceImpl();
-
-ServiceConfig<GenericService> service = new ServiceConfig<GenericService>();
-service.setApplication(application);
-service.setInterface("com.alibaba.dubbo.samples.generic.api.HelloService");
-service.setRef(genericService);
-service.export();
-
-ServiceConfig<GenericService> service2 = new ServiceConfig<GenericService>();
-service2.setApplication(application);
-service2.setInterface("com.alibaba.dubbo.samples.generic.api.HiService");
-service2.setRef(genericService);
-service2.export();
-```
-
-Similarly, you can expose the service using XML configuration; in this case, the server does not depend on the two interfaces HiService and HelloService.
-
-### Service invoke on the consumer
-
-```java
-ApplicationConfig application = new ApplicationConfig();
-application.setName("api-generic-consumer");
-
-RegistryConfig registry = new RegistryConfig();
-registry.setAddress("zookeeper://127.0.0.1:2181");
-
-application.setRegistry(registry);
-
-ReferenceConfig<GenericService> reference = new ReferenceConfig<GenericService>();
-// weak type interface name
-reference.setInterface(HiService.class);
-reference.setApplication(application);
-
-HiService hiService = (HiService) reference.get();
-System.out.println(hiService.hi("dubbo"));
-
-ReferenceConfig<GenericService> reference2 = new ReferenceConfig<GenericService>();
-// weak type interface name
-reference2.setInterface(HelloService.class);
-reference2.setApplication(application);
-
-HelloService helloService = (HelloService) reference2.get();
-System.out.println(helloService.hello("community"));
-```
-
-Similarly, the consumer can also reference the service using an XML configuration and then make the call. Here you can see that the calling method is a normal service call, not a generic call. Of course, it is also possible to use generic calls.
-
-So far, a simple service Mock platform has been successfully launched!
-
-
-## Others
-
-- The generic invoke and generic interface implementations introduced in this article are all based on the native Dubbo protocol. Prior to version 2.6.2, other protocols such as http/hessian don't support generic invoke. Version 2.6.3 will support the generic invoke of these two protocols.
-- The relevant sample codes mentioned in this article can be found in dubbo-samples: https://github.com/apache/dubbo-samples/tree/master/java/dubbo-samples-generic
diff --git a/blog/en-us/dubbo-invoke.md b/blog/en-us/dubbo-invoke.md
deleted file mode 100644
index 56422dd..0000000
--- a/blog/en-us/dubbo-invoke.md
+++ /dev/null
@@ -1,221 +0,0 @@
----
-title: Dubbo: Several ways about synchronous/asynchronous invoke
-keywords: Dubbo, Invoke, Async
-description: This article introduces you how to use Dubbo synchronously or asynchronously.
----
-
-# Dubbo: Several ways about synchronous/asynchronous invoke
-
-As we all know，Dubbo adopts a single large join protocol by default and takes the NIO asynchronous communication mechanism of Netty as the low-level implementation. Based on this mechanism, Dubbo implements several invocation modes as follows:
-
-* synchronous invoke
-* asynchronous invoke
-* parameters callback
-* event notification
-
-### Synchronous invoke
-
-Synchronous invoke is a kind of blocking invocation mode, that is the Consumer keeps blocking and waiting, until the Provider returns.
-
-Generally, a typical synchronous invocation process is as follows:
-
-1. Consumer service thread invokes the remote API and sends requests to the Provider. Meanwhile, the current service thread stays in blocking state;
-2. Provider process relative request after receiving it from Consumer. Then returns the results to Consumer;
-3. After Consumer receiving results, the current thread continues to execute.
-
-Here are two problems:
-
-1. How does Consumer service thread turn into `blocking` state?
-2. How does the service thread be awaked to execute after Consumer receiving results?
-
-In fact, the low-level I/O operations of Dubbo are all asynchronous. The Consumer gets a Future object after invoking the Provider. For synchronous invoke, the service thread takes advantage of `Future#get(timeout)` to block and wait for Provider returning results, with the 'timeout' indicating the timeout defined by Consumer. When the result returns, the Future will be set and the blocked service thread will be awaked. The service thread will return an exception if there is no result af [...]
-
-### Asynchronous invoke
-
-For scenarios that Provider has a long response time, it's necessary to implement asynchronous invoke based on Dubbo's underlying asynchronous NIO. It could utilize the resource of Consumer effectively, and costs less than using multi-thread for Consumer.
-
-Asynchronous invoke does not need specific configuration for Provider. In the example，the API of Provider is defined as follow：
-
-```java
-public interface AsyncService {
- String goodbye(String name);
-}
-```
-
-##### Consumer configuration
-
-```xml
-<dubbo:reference id="asyncService" interface="com.alibaba.dubbo.samples.async.api.AsyncService">
- <dubbo:method name="goodbye" async="true"/>
-</dubbo:reference>
-```
-
-Notice that if we need an asynchronous revoke method, we must use `<dubbo:method/>` label to describe it.
-
-##### Consumer triggers invocation
-
-```java
-AsyncService service = ...;
-String result = service.goodbye("samples");// returns NULL and DO NOT use!
-Future<String> future = RpcContext.getContext().getFuture();
-... // other service thread logic
-result = future.get(); // could use get(timeout, unit) to configure timeout, when it needs to get the asynchronous result
-```
-
-After Dubbo Consumer triggers invocation, it uses `RpcContext.getContext().getFuture()` to get the relative `Future` object, and then it could start executing other tasks. Anytime when we need results, `future.get(timeout)` is supposed to be called.
-
-Under several special conditions, it could be set whether to wait for sending the request, to accelerate the return of invocation:
-
-* `sent="true"` Waiting for sending the request, and return an exception if it fails;
-* `sent="false"` Do not wait for the request, and returns immediately after putting the request to the I/O queue.
-
-We set it to `false` by default. And detailed configuration is as follows：
-
-```xml
-<dubbo:method name="goodbye" async="true" sent="true" />
-```
-
-If you only want to be asynchronous, then omit the result thoroughly, `return="false"` could be set to reduce the creation and management cost of Future:
-
-```xml
-<dubbo:method name="goodbye" async="true" return="false"/>
-```
-
-At this time，`RpcContext.getContext().getFuture()` will return `null`。
-
-The complete sequence diagram of asynchronous invoke is as follow:
-
-
-
-The sample locates at：https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-async
-
-### Parameters callback
-
-The parameter Callback is somewhat similar to the local Callback mechanism, but Callback is not an inner class or interface of Dubbo. Instead, it is defined by the Provider. Dubbo will generate a reverse proxy based on the long connection, so as to implement the logic of calling the Consumer from the Provider.
-
-##### Service and Callback definition of Provider
-
-```java
-public interface CallbackService {
- void addListener(String key, CallbackListener listener);
-}
-
-public interface CallbackListener {
- void changed(String msg);
-}
-```
-
-##### Service implementation of Provider
-
-```java
-public class CallbackServiceImpl implements CallbackService {
-
- private final Map<String, CallbackListener> listeners = new ConcurrentHashMap<String, CallbackListener>();
-
- public CallbackServiceImpl() {
- Thread t = new Thread(new Runnable() {
- public void run() {
- while (true) {
- try {
- for (Map.Entry<String, CallbackListener> entry : listeners.entrySet()) {
- try {
- entry.getValue().changed(getChanged(entry.getKey()));
- } catch (Throwable t) {
- listeners.remove(entry.getKey());
- }
- }
- Thread.sleep(5000); // timely trigger change event
- } catch (Throwable t) {
- t.printStackTrace();
- }
- }
- }
- });
- t.setDaemon(true);
- t.start();
- }
-
- public void addListener(String key, CallbackListener listener) {
- listeners.put(key, listener);
- listener.changed(getChanged(key)); // send notification for change
- }
-
- private String getChanged(String key) {
- return "Changed: " + new SimpleDateFormat("yyyy-MM-dd HH:mm:ss").format(new Date());
- }
-}
-```
-
-##### Service exposure of Provider
-
-```xml
-<bean id="callbackService" class="com.alibaba.dubbo.samples.callback.impl.CallbackServiceImpl"/>
-
-<dubbo:service interface="com.alibaba.dubbo.samples.callback.api.CallbackService" ref="callbackService" connections="1" callbacks="1000">
- <dubbo:method name="addListener">
- <dubbo:argument index="1" callback="true"/>
- <!--<dubbo:argument type="com.demo.CallbackListener" callback="true" />-->
- </dubbo:method>
-</dubbo:service>
-```
-
-Here，Provider needs to declare which parameter is the Callback parameter in the method.
-
-##### Callback interface implementation of Consumer
-
-```java
-CallbackService callbackService = ...;
-callbackService.addListener("foo.bar", new CallbackListener() {
- public void changed(String msg) {
- System.out.println("callback1:" + msg);
- }
-});
-```
-
-The implementation class of the Callback interface is on the Consumer, which automatically exports a Callback service when the method is called. Thus during Provider processing the call, if the parameter is determined as Callback, it will generate a proxy. Therefore, when the service implementation class calling the Callback method, it will be passed to the Consumer to execute the code.
-
-The sample code above is located at：https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-callback
-
-This invocation mode is somewhat like message publishing and subscribing, but there is a little difference. For example, when the Consumer completes the export of Callback service, if it restarts later, then the Provider will fail to adjust. Meanwhile it is also a problem for the Provider to clean up the proxy.
-
-### Event notification
-
-Event notification allows the Consumer triggering three events，particularly `oninvoke`, `onreturn`, `onthrow` before calling, after calling or occurring exceptions.
-
-You can specify which events need to be notified during configuring Consumer, such as:
-
-```xml
-<bean id="demoCallback" class="com.alibaba.dubbo.samples.notify.impl.NotifyImpl" />
-
-<dubbo:reference id="demoService" check="false" interface="com.alibaba.dubbo.samples.notify.api.DemoService" version="1.0.0" group="cn">
- <dubbo:method name="sayHello" onreturn="demoCallback.onreturn" onthrow="demoCallback.onthrow"/>
-</dubbo:reference>
-```
-
-Among them，the code of NotifyImpl is as follow：
-
-```java
-public class NotifyImpl implements Notify{
-
- public Map<Integer, String> ret = new HashMap<Integer, String>();
-
- public void onreturn(String name, int id) {
- ret.put(id, name);
- System.out.println("onreturn: " + name);
- }
-
- public void onthrow(Throwable ex, String name, int id) {
- System.out.println("onthrow: " + name);
- }
-}
-```
-
-Here we address that the parameter rules of three methods in the custom Notify interface are as follows:
-
-* `oninvoke` method's parameters are the same as the calling method parameters;
-* `onreturn` method's first parameter is the returned value of calling method，and the others are the same as the calling method;
-* `onthrow` method's first parameter is an invoked exception，and the others are the same as the calling method.
-
-In the above configuration, `sayHello` method is an asynchronous invocation, so the execution of event notification method is also synchronous. You can configure the `async = true` to make method invocation asynchronous, at this moment, event notification method is executed asynchronously. Especially emphasize that `oninvoke` method is executed synchronously, whether is an asynchronous call or not.
-
-Please refer to the sample code for event notification：https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-notify
\ No newline at end of file
diff --git a/blog/en-us/dubbo-k8s.md b/blog/en-us/dubbo-k8s.md
deleted file mode 100644
index 32fb5dc..0000000
--- a/blog/en-us/dubbo-k8s.md
+++ /dev/null
@@ -1,142 +0,0 @@
----
-title: Integrate Dubbo with Kubernetes
-keywords: Dubbo, Kubernetes, K8S
-description: This article will try to register Dubbo service to Kubernetes and integrate with Kubernetes's multi-tenancy security system.
----
-
-# General goal
-
-Dubbo's provider don't care about service registration.Open its Dubbo service port,the declaration and publishment of the service will be executed by Kubernetes.
-Dubbo's consumer directly discovers the corresponding service endpoints of Kubernetes during service discovery procedure, thereby reusing Dubbo's existing microservice channel capabilities.The benefit is that there is no need to rely on any third-party soft-loaded registry and it can be seamlessly integrated into the multi-tenant security system of Kubernetes. Reference demo : [https://github.com/dubbo/dubbo-ubernetes](https://github.com/dubbo/dubbo-Kubernetes)
-
-# Introduction
-
-Kubernates is a hierarchical system with rich secondary development function based on the expansibility.
-
-* First of all, Kubernates's core function is to manage the container cluster. Kubernates manages the storage and calculation of containerized cluster, based on the container runtime (CRI), network interface (CNI) and storage service interface (CSI/FV).
-* Secondly，Kubernates has application-oriented deployment and routing capabilities，including statefulness/statelessness，batch processing and service-oriented applications，especially the application management based on microservices architecture which includes service discovery，service definition and unified configuration on the basis of configmap.
-* Finally, on top of the abstract model of the basic resource (mainly the resources of abstract infrastructure, IaaS) and the application layer is the governance layer, which includes elastic expansion, namespaces/tenants and so on. Naturally, it is a matter of course to set up service about unified log center and omnidirectional monitoring on the Kubernetes based upon the foundational capabilities of atomic inner core.
-
-We will explain the above description with a diagram of Kubernetes Architecture. In 2018, Kubernetes took a qualitative step toward the standard PaaS basement.Someone hold opinions that the reason is the ability for secondary development on the basis of the expansion and someone think the key is declarative programming and strong community operations relying on Google and Redhat. However,I think the essential reason is Layered architecture and the abstract domain modeling in the problem [...]
-
-
-
-
-
-
-From a micro-service architecture perspective, Kubernetes is a micro-service framework (more appropriate than a micro-service platform or toolkit set at this time) in a sense, supporting the basic capabilities of microservices for service discovery/registration. Use the following table to make a brief description.
-
-| The design of microservice | The function of Kubernetes |
-| :--- | :--- |
-| Point 1：API gateway | Ingress |
-| Point 2：Statelessness, distinguish between stateful and stateless applications | Stateless corresponds to Deployment，and stateful corresponds to StatefulSet |
-| Point 3：Horizontal expansion of the database | Headless service points to PaaS service or StatefulSet deployment |
-| Point 4：Cache | Headless service points to PaaS service or StatefulSet deployment |
-| Point 5：Service splitting and service discovery | Service |
-| Point 6：Service orchestration and flexibility | Replicas of deployment |
-| Point 7：Unified configuration center | ConfigMap |
-| Point 8：Unified log center | DaemonSet deploys log agent |
-| Point 9：Circut break, current limiting and downgrade | Service Mesh |
-| Point 10：Comprehensive monitoring | Cadsivor, DaemonSet deploys and monitors Agent |
-
-By the way, the microservices field involves many issues, which can be explained as follows. When building microservices, we will delve into Distributed System, a discipline has a 40-year research background and is rooted in the adaptive system theory. It's a bit complicated, but the concepts it covers are more or less heard for us, and it solves problems that we're familiar with:
-
-* Deployment
-* Delivery
-* APIs
-* Versioning
-* Contracts
-* Scaling / Autoscaling
-* Service Discovery
-* Load Balancing
-* Routing / Adaptive Routing
-* Health Checking
-* Configuration
-* Circuit Breaking
-* Bulk-heads
-* TTL / Deadlining
-* Latency Tracing
-* Service Causal Tracing
-* Distributed logging
-* Metrics Exposure, Collection
-
-For Kubernetes, only a few of problems are solved. Problems such as Dynamic Routing, Stability Control (Circuit Breaking, Bulk-heads, etc.) , Distributed Service Tracking, etc. are all the blank. These problems are exactly what Service Mesh needs to solve, and these also plays an important role in CNCF's Tail Map. Of course, as Dubbo is a basically complete microservices infrastructure (Dubbo is based on the Sidecar which is a common solution for solving cross-language claims in Service [...]
-
-> <span data-type="color" style="color:rgb(119, 119, 119)"><span data-type="background" style="background-color:rgb(255, 255, 255)">A service mesh is a dedicated infrastructure layer for handling service-to-service communication. It's responsible for the reliable delivery of requests through the complex topology of services that comprise a modern, cloud native application.</span></span>
-
-We will know the existing solution, Dubbo integrates the Clould Native Equipment - Kubernetes's basic abilities to solve the microservices's core problems, can be regarded as a Service Mesh solution in a narrow sense, but it can only be used in the Java field. You can understand the above words as a joke, haha.
-
-# T<span data-type="color" style="color:rgb(51, 51, 51)"><span data-type="background" style="background-color:rgb(255, 255, 255)">hought</span></span>/Plan
-
-Kubernetes is a natural address registration center for microservices, similar to zookeeper, VIPserver and Configserver used internally by Alibaba. Specifically, the Pod in Kubernetes is a running instance of the application. The scheduled deployment/start/stop of the Pod will call the API-Server service to maintain its state to ETCD. The service in Kubernetes is coresponded to the concept of the microservices defined as follows.
-
-> A Kubernetes Service is an abstraction layer which defines a logical set of Pods and enables external traffic exposure, load balancing and service discovery for those Pods.
-
-In conclusion, the Kubernetes service has the following characteristics:
-
-* Each Service has a unique name and corresponding IP. IP is automatically assigned by Kubernetes and the name is defined by the developer.
-* Service IP has several manifestations: ClusterIP, NodePort, LoadBalance and Ingress. ClusterIP is mainly used for intra-cluster communication; NodePort, Ingress and LoadBalance, which are used to expose services to access portals outside the cluster.
-
-At first sight, the service of Kubernetes has its own IP, while under the original fixed mindset: Dubbo/HSF service is aggregated by the IP of the entire service cluster, that means, Kubernetes and Dubbo/HSF look like something different in natural, but when carefully thinking, the difference becomes insignificant. Because the only IP under Kubernetes is just a Virtural IP--VIP, behind the vip are multiple endpoints, which is the factual processing node.
-
-Here we only discuss the situation that the Dubbo service in the cluster is accessed in the same Kubernetes cluster, As for the provider outside Kubernetes to access the provider in Kubernetes, since it involves the problem of network address space, and it usually requires GateWay/loadbalance for mapping conversion, which there not detail discussion for this case. Besides, there are two options available for Kubernetes:
-
-1. DNS: The default Kubernetes service is based on the DNS plugin (The latest version of the recommendation is coreDNS), one proposal on Dubbo is about this. since HSF/Dubbo has always highlighted its soft-load address discovery capability, it ignores Static's strategy insteadily, my understanding is that as a service discovery mechanism, the static resolution mechanism is one of the simplest and most needed to support mechanism, you can also refer to Envoy's point of views. While at th [...]
-
- 
-
-2. API：DNS relies on the DNS plugin, which will generate additional operation, so consider directly obtaining the endpoint through the client of Kubernetes. In fact, by accessing the API server interface of Kubernetes, you can directly obtain the list of endpoints behind a certain servie, and can also monitor the changes in its address list. Thereby implementing the soft load discovery strategy recommended by Dubbo/HSF. Refer to the code for details:
-
-The above two thoughts need to consider the following two points:
-
-1. Kubernetes and Dubbo are consistent with the mapping name of service. Dubbo's service is determined by serviename, group, version to determine its uniqueness, and servicename generally has a longer package name for its service interface. Need to map the servie name of Kubernetes and the service name of dubbo. Either add a property like SOFA to define it. This is a big change, but it is most reasonable. Or it is a fixed rule to reference the deployed environment variables, which can be [...]
-2. Port problem:The default Pod and Pod network interoperability is solved, need to be validated.
-
-## Demo Verification
-
-The following is a demo deployment through Kubernetes service in Alibaba Cloud's Container Registry and EDAS. Visit Alibaba Cloud -》Container Registry.
-
-1. Create repo and bind the github codebase. As shown below.
-
-
-
-
-
-
-2. Click Manage enter the repository details page. Click Build in images service panel, construct the demo into image and publish it to the specified repository. As shown below.
-
- 
-
-
-
-3. Switch to Enterprise Distributed Application Services (EDAS) products panel, visit Resource Management -> Clusters. Create Kubernetes cluster and bind ECS. As shown below.
-
- 
-
-
-
-4. Application Management -> Create application, type Kubernetes application and specify the image in the container registry . As shown below.
-
- 
-
-
-
- 
-
-
-
-5. After creation , then deploy applications. As shown below.
-
- 
-
-- The supplementary application name cannot have uppercase letters, all lowercase, otherwise there is a problem of deployment failure.
-
-- When creating an app, after selecting the image, the next button cannot be clicked and you need to click Choose to continue.
-
-- EDAS has two independent Kubernetes services, one based on Alibaba Cloud's container service, and one set by Lark. I experience the latter.
-
-- The development joint of Docker and IDE integration, you need to consider the relevant plug-ins for integrating IDEA.
-
-- There is always an error in deployment, maybe there is a problem with the Kubernetes service. Need further investigation.
-
-{"kind":"Pod","namespace":"lzumwsrddf831iwarhehd14zh2-default","name":"dubbo-k8s-demo-610694273-jq238","uid":"12892e67-8bc8-11e8-b96a-00163e02c37b","apiVersion":"v1","resourceVersion":"850282769"},"reason":"FailedSync","message":"Error syncing pod","
diff --git a/blog/en-us/dubbo-loadbalance.md b/blog/en-us/dubbo-loadbalance.md
deleted file mode 100644
index 6ff42c7..0000000
--- a/blog/en-us/dubbo-loadbalance.md
+++ /dev/null
@@ -1,271 +0,0 @@
----
-title: Dubbo's Load Balance
-keywords: Dubbo, LoadBalance
-description: This article introduces you what is load balance and how load balance strategy is implemented in Dubbo.
----
-
-# Dubbo's Load Balance
-
-## Background
-
-Dubbo is a distributed service framework that avoids single point of failure and horizontal expansion of support services. A service typically deploys multiple instances. How to select a call from a cluster of multiple service providers involves a load balancing strategy.
-
-## Concepts
-
-Before discussing load balancing, I will explain these three concepts first.
-
-1. Load Balancing
-2. Fault-tolerant Cluster
-3. Service Route
-
-These three concepts are confusing. They all describe how to choose from multiple Providers to make calls. So what is the difference between them? Let me give a simple example and explain these concepts clearly.
-
-There is a Dubbo user service, 10 deployed in Beijing and 20 deployed in Shanghai. A service consumer in Hangzhou initiated a call and then the following steps executed:
-
-1. According to the configured routing rule, if the call is initiated by Hangzhou, it will be routed to the nearest 20 Providers in Shanghai.
-2. According to the configured random load balancing strategy, one of the 20 Providers is randomly selected to be called, assuming that the 7th Provider is randomly selected.
-3. As a result, calling the 7th Provider failed.
-4. Retried other servers according to the configured Fault-tolerant Cluster mode.
-5. The call to the 13th Provider was successful.
-
-Steps 1, 2, and 4 above correspond to routing, load balancing, and fault-tolerant cluster. In Dubbo, a subset is selected by routing from multiple Providers according to routing rules, then a Provider selected from the subset according to load balancing to make this call. If the call fails, Dubbo retry or schedule retransmission or fail-fast according to the Fault-tolerant Cluster policy. You can see the routes in Dubbo, load balancing and Fault-tolerant Cluster exectute at different sta [...]
-
-## Dubbo's Internal Load Balancing Strategy
-
-Dubbo has four Internal Load Balancing Strategies:
-
-1. RandomLoadBalance: Random load balancing. Choose a Provider randomly. It is Dubbo's default load balancing strategy.
-2. Round Robin Load Balancing: Polling load balancing, then chooses one Provider.
-3. LeastActiveLoadBalance: The minimum number of active calls, the random number of the same active number. The active number refers to the difference before and after the call. Make slow providers receive fewer requests, because the slower Provider before and after the difference of calls will be larger.
-4. ConsistentHashLoadBalance: Consistent hash load balancing. Requests with the same parameters always fall on the same machine.
-
-### 1. Random Load Balancing
-
-As the name implies, the random load balancing strategy is to select one from multiple Providers randomly. However, random load balancing in Dubbo has a weighting concept that sets the random probability according to the weight. For example, there are 10 Providers, it's not to say that the probability of each Provider is the same, but to assign the probability by combining the weights of these 10 providers.
-
-In Dubbo, you can set weights on the Provider. For example, if the performance of the machine is better, you can set a larger weight. If the performance is poorer, you can set a smaller weight. Weights have an impact on load balancing. The weight of provider can be set in Dubbo Admin.
-
-#### Weight-based Load Balancing Algorithm
-
-The stochastic strategy will determine whether the weights of all the invokers are the same at first. If they are all the same, then the processing is relatively simple. Using `random.nexInt(length)`, you can randomly generate an invoker serial number, and select the corresponding invoker according to the serial number. If the service provider not set weight in Dubbo Admin, then all the invokers have the same weight, the default is 100. If the weights are different, then you need to comb [...]
-
-| Invoker | Weight |
-| ------- | ------ |
-| A | 10 |
-| B | 20 |
-| C | 20 |
-| D | 30 |
-
-The total weight of A, B, C and D is 10 + 20 + 20 + 30 = 80. Spread 80 numbers in the following diagram:
-
-```
-+-----------------------------------------------------------------------------------+
-| | | | |
-+-----------------------------------------------------------------------------------+
-1 10 30 50 80
-
-|-----A----|---------B----------|----------C---------|---------------D--------------|
-
-
----------------------15
-
--------------------------------------------37
-
------------------------------------------------------------54
-```
-
-There are four areas in the above picture, and the lengths are the weights of A, B, C and D, respectively. Use `random.nextInt(10 + 20 + 20 + 30)` to randomly select one of the 80 numbers. Then determine which area the number is distributed in. For example, if random to 37, 37 is distributed in the C region, then select inboker C. 15 is in the B area, 54 is in the D area.
-
-#### Random load balancing Source code
-
-Below is the source code for random load balancing. For ease of reading and understanding, I removed the extraneous parts.
-
-```
-public class RandomLoadBalance extends AbstractLoadBalance {
-
- private final Random random = new Random();
-
- protected <T> Invoker<T> doSelect(List<Invoker<T>> invokers, URL url, Invocation invocation) {
- int length = invokers.size(); // total invoker
- int totalWeight = 0; // Sum of invokers' weights
-
- // Determine if all the invokers have the same weight
- // If the weights are the same, it is simple to generate an index directly from Random.
- boolean sameWeight = true;
- for (int i = 0; i < length; i++) {
- int weight = getWeight(invokers.get(i), invocation);
- totalWeight += weight; // Sum
- if (sameWeight && i > 0 && weight != getWeight(invokers.get(i - 1), invocation)) {
- sameWeight = false;
- }
- }
-
- if (totalWeight > 0 && !sameWeight) {
- // If not all of the invoker weights are the same, load balancer will randomly choose invoker based on its weight. The greater the weight, the greater the probability of being selected
- int offset = random.nextInt(totalWeight);
- for (int i = 0; i < length; i++) {
- offset -= getWeight(invokers.get(i), invocation);
- if (offset < 0) {
- return invokers.get(i);
- }
- }
- }
- // If all invokers have the same weight
- return invokers.get(random.nextInt(length));
- }
-}
-```
-
-### 2. Round Robin Load Balancing
-
-Round Robin Load Balancing, is to call all Providers in turn. As with random load balancing strategies, Round Robin Load Balancing policies also has a weighting concept. The Round Robin Load Balancing algorithm allows RPC calls to be allocated exactly as we set. Whether it is a small or large number of calls. However, there are also some shortcomings in the Round Robin Load Balancing algorithm. There is a problem that the slow provider accumulates the request. For example, the second mac [...]
-### 3. Minimum Active Call Load Balancing
-Official explanation:
-> The active number refers to the difference between the counts before and after the call. Select the machine with the minimum number of active calls or choose a random one among machines with the same active number, so that the slower machine can receives less requests.
-
-This explanation seems to be ambigious. We know the purpose is to ensure the slower machine receive less requests, but it is not clear how to achieve it. An example is here: each service maintains an active number counter. When A machine starts processing the request, the counter is incremented by 1. At this time, A is still processing. If the processing is completed, the counter is decremented by 1. B machine processes very quickly after receiving the request. Then the active numbers of [...]
-
-When processing a new request, Consumer will check the active number of all Providers. If there is only one Invoker with the minimum active number, the Invoker is returned directly.
-
-```
-if (leastCount == 1) {
- // if there is only one minimum value then return directly
- return invokers.get(leastIndexs[0]);
-}
-```
-
-If there are multiple Invokers with the minimum active number, plus the weights are not equal and the total weight is greater than 0, then generate a random weight ranging from 0 to totalWeight. Finally, the Invoker is selected based on the randomly generated weights.
-
-```
-if (! sameWeight && totalWeight > 0) {
- // if the weights are not equal and the toatl weight is greater than 0 then choose randomly according to total weight
-
- int offsetWeight = random.nextInt(totalWeight);
-
- // and determine which segment the random value falls on.
-
- for (int i = 0; i < leastCount; i++) {
- int leastIndex = leastIndexs[i];
- offsetWeight -= getWeight(invokers.get(leastIndex), invocation);
- if (offsetWeight <= 0)
- return invokers.get(leastIndex);
- }
-}
-```
-
-
-### 4. Consistent Hash Algorithm
-
-Use consistent hash algorithm to ensure that requests with same parameters are always sent to the same Provider. When a Provider crashes, requests originally sent to the Provider is spread evenly to other Providers based on the virtual node without causing drastic changes. The algorithm can be seen at: http://en.wikipedia.org/wiki/Consistent_hashing
-
-By default, only the first parameter is hashed. Configure if you would like to modify it:
-```
-<dubbo:parameter key="hash.arguments" value="0,1" />
-```
-
-By default, 160 virtual nodes are used. Configure if you would like to modify it:
-```
-<dubbo:parameter key="hash.nodes" value="320" />
-```
-
-Consistent hash algorithms can be used in conjunction with caching mechanisms. For example, there is a service getUserInfo(String userId). After the hash algorithm is set, the same userId call is sent to the same Provider. This Provider can cache user data in memory, reducing the number of accesses to the database or distributed cache. If this part of the data is allowed to be inconsistent for some time, this approach can be considered. The number of dependencies and accesses to middlewa [...]
-
-
-
-
-## Load Balancing Configuration
-
-If load balancing is not specified, random load balancing is used by default. Load balancing can also be explicitly specified based on our needs. Load balancing can be configured in multiple local classes, such as Provider Side, Consumer Side, Service Level, and Method Level.
-
-### Server Side Service Level
-```
-<dubbo:service interface="..." loadbalance="roundrobin" />
-```
-All methods of the service use roundrobin load balancing.
-
-### Client Side Service Level
-```
-<dubbo:reference interface="..." loadbalance="roundrobin" />
-```
-All methods of the service use roundrobin load balancing.
-
-### Server Side Method Level
-```
-<dubbo:service interface="...">
- <dubbo:method name="hello" loadbalance="roundrobin"/>
-</dubbo:service>
-```
-Only the hello method of the service uses roundrobin load balancing.
-
-### Client Side Method Level
-```
-<dubbo:reference interface="...">
- <dubbo:method name="hello" loadbalance="roundrobin"/>
-</dubbo:reference>
-```
-Only the hello method of the service uses roundrobin load balancing.
-
-Similar to other Dubbo configurations, multiple configurations are covered:
-
-1. The method level takes precedence, the interface level is next, and the global configuration comes last.
-2. If the level is the same, the Consumer is given priority and the Provider is next
-
-Therefore, the priority of the above four configurations is:
-
-1. Client side method level configuration.
-2. Client side interface level configuration.
-3. Server side method level configuration.
-4. Server side interface level configuration.
-
-
-
-
-## Extended Load Balancing
-
-Four load balancing implementations of Dubbo meet the requirements in most cases. Sometimes, we may need to implement our own load balancing strategy because of the needs of the business. This chapter only explains how to configure the load balancing algorithm. For more on the Dubbo extension mechanism, go to the Dubbo extension mechanism practice.
-
-1. Implementing the LoadBalance interface
-
-The following is Dubbo's LoadBalance interface:
-```
-@SPI(RandomLoadBalance.NAME)
-public interface LoadBalance {
- @Adaptive("loadbalance")
- <T> Invoker<T> select(List<Invoker<T>> invokers, URL url, Invocation invocation) throws RpcException;
-}
-```
-
-This is the interface of the SPI. The parameters of the select method are as follows:
-
-* invokers: A list of all service Providers.
-* url: Some configuration information, such as interface name, check or not, serialization.
-* invocation: Information called by the RPC, including the method name, method parameter type, and method parameters. Here is a LoadBalance implemented by us. The implementation is very simple - Choose the first Invoker:
-```
-package com.demo.dubbo;
-public class DemoLoadBalance implements LoadBalance {
- @Override
- public <T> Invoker<T> select(List<Invoker<T>> invokers, URL url, Invocation invocation) throws RpcException {
- System.out.println("[DemoLoadBalance]Select the first invoker...");
- return invokers.get(0);
- }
-}
-```
-
-2. Add a resource file
-
-Add a file:
-``src/main/resource/META-INF/dubbo/com.alibaba.dubbo.rpc.cluster.LoadBalance``
-This is a simple text file. The file contents are as follows:
-```
-demo=my=com.demo.dubbo.DemoLoadBalance
-```
-
-3. Configure to use custom LoadBalance
-
-```
-<dubbo:reference id="helloService" interface="com.demo.dubbo.api.IHelloService" loadbalance="demo" />
-```
-
-Configure ``<loadbalance="demo">`` in ``dubbo:reference`` at the Consumer side.
-
-After 3 steps above, we wrote a custom LoadBalance and told Dubbo to use it. Start Dubbo and we can see that Dubbo has used a custom DemoLoadBalance.
diff --git a/blog/en-us/dubbo-meetup-beijing-may-12th-2018.md b/blog/en-us/dubbo-meetup-beijing-may-12th-2018.md
deleted file mode 100644
index cdfbbd7..0000000
--- a/blog/en-us/dubbo-meetup-beijing-may-12th-2018.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: The first Dubbo meetup has been held in Beijing
-keywords: Dubbo, Beijing, meetup
-description: The first Dubbo meetup has been held in Beijing.
----
-
-The first Dubbo meetup has been held in Beijing
----
-
-The first Dubbo meetup has successfully been held in Beijing, over 400+ people were present. What a great event!
-
-Please enjoy the slides of the topics:
- * Ian Luo: Dubbo's present and future (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/dubbo-present-and-future.pdf)
- * Jun Liu: Introduction to the 4th Aliware Performance Challenge (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/introduction-to-4th-aliware-performance-challenge.pdf)
- * Zhixuan Chen: Quickly building Microservice with Dubbo and Spring-boot (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/quickly-building-microservice-with-dubbo-and-springboot.pdf)
- * Xin Wang: Dubbo and Weidian's Practice on Microservice Architecture (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/dubbo-and-weidian's-practice-on-microservice-architecture.pdf)
diff --git a/blog/en-us/dubbo-meetup-chengdu.md b/blog/en-us/dubbo-meetup-chengdu.md
deleted file mode 100644
index 87d6f0f..0000000
--- a/blog/en-us/dubbo-meetup-chengdu.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: The fourth Dubbo meetup has been held in Chengdu
-keywords: Dubbo, Chengdu, meetup
-description: The fourth Dubbo meetup has been held in Chengdu.
----
-
-# The fourth Dubbo meetup has been held in Chengdu
-
-
-
-## The depth of the user communication
-
-On August 26, 10:00 am - 12:00am, invited the arrival of the car to help, cloud gold, former BBD, flying fish star four companies open source enthusiasts and heavy users participate in face-to-face communication;According to the participants' feedback, answer to Dubbo many doubt, especially how to participate in the contribution to the community, as well as code contribution value point.Hope later can be more deeply involved in Dubbo communities and activities.
-
-## Meetup activity information
-
-The event is still full, total enrollment of 976, 350 + site users, live PV 13207.
-
-
-## The registration information
-
-Aliware Open Source, headquarters - Apache Dubbo developers salon on August 26 (Sunday) in chengdu high-tech zone tianfu hemicyenine rong international plaza, 200 five street on the 8th floor held the second floor conference room, technical thinking is GG feast, dry goods and welfare will not one less.</br>
-Sign up link：http://www.huodongxing.com/event/7453091088400
-
-<img src="../../img/blog/dubbo-chengdu-meetup-img.jpg"/>
diff --git a/blog/en-us/dubbo-meetup-hangzhou.md b/blog/en-us/dubbo-meetup-hangzhou.md
deleted file mode 100644
index 8e85346..0000000
--- a/blog/en-us/dubbo-meetup-hangzhou.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: The fifth Dubbo meetup has been held in Hangzhou
-keywords: Dubbo, Hangzhou, meetup
-description: The fifth Dubbo meetup has been held in Hangzhou
----
-
-# The fifth Dubbo meetup has been held in Hangzhou
-
-
-The fifth Dubbo meetup has been held in Hangzhou,
-
-Please enjoy the slides of the topics:
- * Ding Li: How to involve in dubbo community [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/how-to-involve-in-dubbo-community.pdf)
- * Shenli Cao: Dubbo 2.7 introduction [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/dubbo-2.7-introduction.pdf)
- * Tao Yang: Dubbo practice in netease koala [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/dubbo-practice-in-netease-koala.pdf)
- * Mercy Ma: Nacos support in Dubbo [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/nacos-support-in-dubbo.pdf)
- * Yihao Zhao: Sentinel: Sentinel support for Dubbo [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/sentinel-support-for-dubbo.pdf)
- * Zhixuan Chen: Troubleshooting Dubbo with Arthas [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201812%40hangzhou/troubleshooting-dubbo-with-arthas.pdf)
-
diff --git a/blog/en-us/dubbo-meetup-shanghai-jun-23rd-2018.md b/blog/en-us/dubbo-meetup-shanghai-jun-23rd-2018.md
deleted file mode 100644
index eab16c4..0000000
--- a/blog/en-us/dubbo-meetup-shanghai-jun-23rd-2018.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: The second Dubbo Shanghai meetup has been held successfully
-keywords: Dubbo, Shanghai, meetup
-description: The second Dubbo Shanghai meetup has been held successfully.
----
-
-The second Dubbo Shanghai meetup has been held successfully
----
-
-The sencond Dubbo meetup has successfully been held in Shanghai, over 700 people submitted registration, and over 300 were present, more than 10,000 watched the live online.
-
-Please enjoy the slides of the topics:
- * Jerrick Zhu: Dubbo Status and Roadmap (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201806%40Shanghai/dubbo-status-and-roadmap.pdf)
- * Mercy Ma: Dubbo Cloud Native Practices and Thoughts (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201806%40Shanghai/dubbo-cloud-native-practices-and-thoughts.pdf)
- * Ping Guo: Nacos Open Source Initiative (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201806%40Shanghai/nacos-open-source-initiative.pdf)
- * Zhiwei Pan: Dubbo Practices on Internet Finance Industries (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201806%40Shanghai/dubbo-practices-on-internet-finance-industries.pdf)
diff --git a/blog/en-us/dubbo-meetup-shenzhen.md b/blog/en-us/dubbo-meetup-shenzhen.md
deleted file mode 100644
index 21ed311..0000000
--- a/blog/en-us/dubbo-meetup-shenzhen.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: The third Dubbo meetup has been held in Shenzhen
-keywords: Dubbo, Shenzhen, meetup
-description: The third Dubbo meetup has been held in Shenzhen
----
-
-The third Dubbo meetup has been held in Shenzhen
----
-
-The third Dubbo meetup has successfully been held in Shenzhen, over 2000 people submitted registration, and over 700 were present, more than 17,000 watched the live online.
-
-Please enjoy the slides of the topics:
- * Zhixuan Chen: Dubbo-present-and-2.7-update (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201807%40shenzhen/dubbo-present-and-2.7-update.pdf)
- * Bin Kang: Microservice-in-lexinfintech (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201807%40shenzhen/microservice-in-lexinfintech.pdf)
- * Jialiang lin: sentinel (Chinese) [slides](https://github.com/dubbo/awesome-dubbo/blob/master/slides/meetup/201807%40shenzhen/sentinel.pdf)
diff --git a/blog/en-us/dubbo-new-async.md b/blog/en-us/dubbo-new-async.md
deleted file mode 100644
index 585b7fd..0000000
--- a/blog/en-us/dubbo-new-async.md
+++ /dev/null
@@ -1,585 +0,0 @@
----
-title: How to implement a fully asynchronous calls chain based on Dubbo
-keywords: Dubbo, asynchronous, async chain
-description: This article recalls how asynchronous call is implemented in Dubbo 2.6.x, and introduces the new way based on CompletableFuture in 2.7.0.
----
-
-
-# How to implement a fully asynchronous calls chain based on Dubbo
-
-Implementing the full asynchronous programming based on Dubbo, which is a new feature introduced in version 2.7.0 after the enhancement of the existing asynchronous mode.This article first reviews the supported functions and existing problems of asynchronization in 2.6.x and earlier versions, and introduces the targeted enhancements based on CompletableFuture in version 2.7.0. Then, the use of enhanced asynchronous programming is elaborated through several examples. Finally, it summarize [...]
-
-## Asynchronous mode before version 2.6.x
-
-Dubbo Provides some asynchronous programming capabilities in 2.6.x and earlier versions, including [Asynchronous Call](http://dubbo.apache.org/zh-cn/docs/user/demos/async-call.html), [Parameter Callback](http://dubbo.apache.org/zh-cn/docs/user/demos/callback-parameter.html) and [Event Notification](http://dubbo.apache.org/zh-cn/docs/user/demos/events-notify.html) on Consumer side. There are some brief introductions to the usage and Demo in the above document links.
-
-But the current asynchronous method has the following problems:
-
-- Methods to access Future object are not direct enough.
-- Future interface cannot implement automatic callback. Customized ResponseFuture class could implement callback, however it only supports limited asynchronous scenes. For example, it does not support mutual coordination or combination between Future objects.
-- Asynchronization on Provider side is not supported.
-
-Take the asynchronous method of Consumer side as an example:
-
-1. Define a original synchronous interface and add the declaration to support asynchronous calls.
-
-```
-public interface FooService {
- String findFoo(String name);
-}
-```
-
-```
-<dubbo:reference id="fooService" interface="com.alibaba.foo.FooService">
- <dubbo:method name="findFoo" async="true" />
-</dubbo:reference>
-```
-
-2. Obtain Future object through RpcContext.
-
-```
-// this call will return null immediately
-fooService.findFoo(fooId);
-// Obtain the Future instance. When the result is returned, Future instance will be notified and the result will be set to Future instance.
-Future<Foo> fooFuture = RpcContext.getContext().getFuture();
-fooFuture.get();
-```
-
-or
-
-```
-// this call will return null immediately
-fooService.findFoo(fooId);
-// get Dubbo's built-in ResponseFuture, and set the callback
-ResponseFuture future = ((FutureAdapter)RpcContext.getContext().getFuture()).getFuture();
-future.setCallback(new ResponseCallback() {
- @Override
- public void done(Object response) {
- System.out.print(response);
- }
-
- @Override
- public void caught(Throwable exception) {
- exception.printStackTrace();
- }
-});
-```
-
-From this simple example, we can see there are some inconveniences in use:
-
-1. The synchronization interface of findFoo cannot directly return a Future object representing the asynchronous result, which is further obtained through RpcContext.
-2. Future object can only be obtained from get method that will block until getting the result.
-3. Callback can be set by getting the built-in ResponseFuture interface. However, the API to obtain ResponseFuture is not convenient enough to support other asynchronous scenes except callback. For example, it does not support the scene where multiple Future objects work together.
-
-## Enhancement based on CompletableFuture in version 2.7.0
-
-People who understand the evolution history of Future in Java should know that the Future used in Dubbo 2.6.x and earlier versions is introduced in Java 5, so there are some problems in function design.The CompletableFuture introduced in Java 8 further enriches the Future interface and solves these problems well.
-
-Support for Java 8 has been upgraded in Dubbo 2.7.0, and Dubbo has enhanced the current asynchronous functionality based on CompletableFuture.
-
-1. Now it supports direct definition of service interfaces that return CompletableFuture. Through these interfaces, we can implement asynchronous programming on both Consumer side and Provider side more naturally.
-
-
-
-
-
- ```
- public interface AsyncService {
- CompletableFuture<String> sayHello(String name);
- }
- ```
-
-
-
-
-
-2. If you don't want to define the return value of the interface as a Future object, or if there is a defined synchronization interface, you can additionally define an asynchronous interface and provide a method to return a Future object.
-
-
-
- ```
- public interface AsyncService {
- CompletableFuture<String> sayHello(String name);
- }
- ```
-
-
-
- ```
- @AsyncFor(AsyncService.class)
- public interface GrettingServiceAsync extends GreetingsService {
- CompletableFuture<String> sayHiAsync(String name);
- }
- ```
-
-
-
- In this way, Provider can only implement the sayHi method. The Consumer can get a Future instance by directly calling sayHiAsync, and Dubbo framework will convert it to a call to the sayHi method on the Provider side automatically.
-
-
-
- Providing an asynchronous method definition for each synchronization method can be inconvenient. Further, using [Annotation Processor implementation](https://github.com/dubbo/dubbo-async-processor) in the Dubbo ecosystem can automatically generate asynchronous method definitions for us.
-
-3. Similarly, if your original interface definition doesn't return a Future object, the Provider side also provides a programming interface similar to the Async Servlet in Servlet 3.0 to support asynchronization : `RpcContext.startAsync()`.
-
-
-
- ```
- public interface AsyncService {
- String sayHello(String name);
- }
- ```
-
-
-
- ```
- public class AsyncServiceImpl implements AsyncService {
- public String sayHello(String name) {
- final AsyncContext asyncContext = RpcContext.startAsync();
- new Thread(() -> {
- asyncContext.write("Hello " + name + ", response from provider.");
- }).start();
- return null;
- }
- }
- ```
-
-
- At the beginning of the method body, it starts asynchronization by running `RpcContext.startAsync()` , and it starts a new thread to execute the business logic asynchronously. After the time-consuming operation is completed, the result is written back by `asyncContext.write`.
-
-4. RpcContext returns CompletableFuture directly.
-
-
-
- ```
- CompletableFuture<String> f = RpcContext.getContext().getCompletableFuture();
- ```
-
-All of the above enhancements are based on the compatibility with existing asynchronous programming, so asynchronous programs written based on 2.6.x versions can be successfully compiled without any modification.
-
-Next, let's illustrate how to implement a fully asynchronous Dubbo service call chain through a few examples.
-
-
-## example 1：CompletableFuture interface
-
-CompletableFuture interface can be used both for a synchronous call and for an asynchronous call on Consumer or Provider side. This example implements asynchronous calls between Consumer and Provider sides. Code link [dubbo-samples-async-original-future](https://github.com/apache/dubbo-samples/tree/master/dubbo-samples-async/dubbo-samples-async-original-future
-).
-
-1. Interface definition
-
-
-
- ```
- public interface AsyncService {
- CompletableFuture<String> sayHello(String name);
- }
- ```
-
-
-
- Note that the return type of this interface is `CompletableFuture<String>`.
-
-
-2. Provider Side
-
-
-
- - Implementation
-
-
-
- ```
- public class AsyncServiceImpl implements AsyncService {
- public CompletableFuture<String> sayHello(String name) {
- return CompletableFuture.supplyAsync(() -> {
- try {
- Thread.sleep(5000);
- } catch (InterruptedException e) {
- e.printStackTrace();
- }
- return "async response from provider.";
- });
- }
- }
- ```
-
-
- We can see that the business code is switched to be executed in the new thread by supplyAsync, so the Provider side is asynchronous.
-
- - Config
-
-
-
- ```
- <bean id="asyncService" class="com.alibaba.dubbo.samples.async.impl.AsyncServiceImpl"/>
- <dubbo:service interface="com.alibaba.dubbo.samples.async.api.AsyncService" ref="asyncService"/>
- ```
-
-
-
- The Config is the same as the original interface.
-
-3. Consumer Side
-
-
-
- - Config
-
-
-
- ```
- <dubbo:reference id="asyncService" timeout="10000" interface="com.alibaba.dubbo.samples.async.api.AsyncService"/>
- ```
-
-
-
- The Config is the same as the original interface.
-
-
-
- - Call remote service
-
-
-
- ```
- public static void main(String[] args) throws Exception {
- ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[]{"META-INF/spring/async-consumer.xml"});
- context.start();
- final AsyncService asyncService = (AsyncService) context.getBean("asyncService");
-
- CompletableFuture<String> future = asyncService.sayHello("async call request");
- future.whenComplete((v, t) -> {
- if (t != null) {
- t.printStackTrace();
- } else {
- System.out.println("Response: " + v);
- }
- });
- System.out.println("Executed before response return.");
- System.in.read();
- }
- ```
-
-
-
- `CompletableFuture<String> future = asyncService.sayHello("async call request");`It is convenient to return the Future instance, which implements the asynchronous service call on the Consumer side.
-
-## Example 2：Synchronous interface uses Annotation Processor
-
-This example demonstrates how to implement the Consumer-side asynchronous service call using the Annotation Processor based on the original synchronous interface. Code link [dubbo-samples-async-generated-future](https://github.com/apache/dubbo-samples/tree/master/dubbo-samples-async/dubbo-samples-async-generated-future).
-
-1. Interface definition
-
-
-
- ```
- @DubboAsync
- public interface GreetingsService {
- String sayHi(String name);
- }
- ```
-
-
-
- This is a generic definition of the Dubbo service interface. Note that add the @DubboAsync annotation when using Annotation Processor.
-
-
- ```
- <dependency>
- <groupId>com.alibaba</groupId>
- <artifactId>dubbo-async-processer</artifactId>
- <version>1.0.0-SNAPSHOT</version>
- </dependency>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-compiler-plugin</artifactId>
- <version>3.7.0</version>
- <configuration>
- <source>1.8</source>
- <target>1.8</target>
- <annotationProcessorPaths>
- <path>
- <groupId>com.alibaba</groupId>
- <artifactId>dubbo-async-processer</artifactId>
- <version>1.0.0-SNAPSHOT</version>
- </path>
- </annotationProcessorPaths>
- </configuration>
- </plugin>
- ```
-
-
-
- The above config is the Maven dependency that imports dubbo-async-processer processor. Developers who define interfaces (providing APIs) usually add the above dependencies to the project, so that when doing API packaging, the following interface definitions will be automatically generated in APIs:
-
-
- ```
- /**
- * Generated by dubbo-async-processer
- */
- package com.alibaba.dubbo.samples.api;
- import java.util.concurrent.CompletableFuture;
- @javax.annotation.Generated("com.alibaba.dubbo.async.processor.AsyncAnnotationProcessor")
- @org.apache.dubbo.common.config.AsyncFor(com.alibaba.dubbo.samples.api.GreetingsService.class)
- public interface GreetingsServiceAsync extends GreetingsService {
- CompletableFuture<java.lang.String> sayHiAsync(java.lang.String name);
- }
- ```
-
-
-
-
-
-2. Provider side
-
-
-
- - Config
-
-
-
- ```
- <bean id="greetingsService" class="com.alibaba.dubbo.samples.async.impl.GreetingsServiceImpl"/>
- <dubbo:service interface="com.alibaba.dubbo.samples.api.GreetingsService" ref="greetingsService"/>
- ```
-
-
-
- - Service implementation
-
-
-
- ```
- public class GreetingsServiceImpl implements GreetingsService {
- @Override
- public String sayHi(String name) {
- return "hi, " + name;
- }
- }
- ```
-
-3. Consumer side
-
-
-
- - Config
-
-
-
- ```
- <dubbo:reference id="greetingsService" interface="com.alibaba.dubbo.samples.api.GreetingsServiceAsync"/>
- ```
-
-
-
- Note that the service interface uses **GreetingsServiceAsync**
-
-
-
- - Service call
-
-
-
- ```
- public static void main(String[] args) throws Exception {
- ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[]{"META-INF/spring/async-consumer.xml"});
- context.start();
-
- GreetingsServiceAsync greetingsService = (GreetingsServiceAsync) context.getBean("greetingsService");
- CompletableFuture<String> future = greetingsService.sayHiAsync("async call reqeust");
- System.out.println("async call ret :" + future.get());
-
- System.in.read();
- }
- ```
-
-
-
- In this way, we can use `CompletableFuture<String> future = greetingsService.sayHiAsync("async call reqeust");` directly，and return CompletableFuture.
-
-## Example 3：Use AsyncContext
-
-This example demonstrates how to implement the Provider-side asynchronous execution through AsyncContext based on the original synchronous interface. Code link [dubbo-samples-async-provider](https://github.com/apache/dubbo-samples/tree/master/dubbo-samples-async/dubbo-samples-async-provider).
-
-1. Interface definition
-
-
-
- ```
- public interface AsyncService {
- String sayHello(String name);
- }
- ```
-
-
-
-
-
-2. Provider side
-
-
-
- - Config
-
-
-
- ```
- <bean id="asyncService" class="com.alibaba.dubbo.samples.async.impl.AsyncServiceImpl"/>
- <dubbo:service async="true" interface="com.alibaba.dubbo.samples.async.api.AsyncService" ref="asyncService"/>
- ```
-
-
-
- Note that adding `async="true"` indicates that this is a service that starts the Provider-side execution asynchronously.
-
-
-
- - Asynchronous execution implementation
-
-
-
- ```
- public class AsyncServiceImpl implements AsyncService {
- public String sayHello(String name) {
- final AsyncContext asyncContext = RpcContext.startAsync();
- new Thread(() -> {
- asyncContext.signalContextSwitch();
- try {
- Thread.sleep(500);
- } catch (InterruptedException e) {
- e.printStackTrace();
- }
- asyncContext.write("Hello " + name + ", response from provider.");
- }).start();
- return null;
- }
- }
- ```
-
-3. Consumer side
-
-
-
- - Config
-
-
-
- ```
- <dubbo:reference id="asyncService" interface="com.alibaba.dubbo.samples.async.api.AsyncService"/>
- ```
-
-
-
- - Service call
-
-
-
- ```
- public static void main(String[] args) throws Exception {
- ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[]{"META-INF/spring/async-consumer.xml"});
- context.start();
-
- AsyncService asyncService = (AsyncService) context.getBean("asyncService");
- System.out.println(asyncService.sayHello("async call request"));
-
- System.in.read();
- }
- ```
-
-## New problems resulted from asynchronization
-
-### Filter Chain
-
-The following is a complete Filter chain for a normal Dubbo call.
-
-After using the asynchronous call, since the asynchronous result is executed separately in the asynchronous thread, the Result passed through the second half of the Filter chain is null, and the real result cannot be processed by the Filter chain when it is returned.
-
-In order to solve this problem, PostProcessFilter and AbstractPostProcessFilter were introduced in Dubbo 2.7.0. The PostProcessFilter interface extends from the Filter interface, and AbstractPostProcessFilter is an abstract implementation of PostProcessFilter.
-
-The following is an example of extending the Filter and supporting the asynchronous Filter chain.
-
-```
-@Activate(group = {Constants.PROVIDER, Constants.CONSUMER})
-public class AsyncPostprocessFilter extends AbstractPostProcessFilter {
-
- @Override
- public Result invoke(Invoker<?> invoker, Invocation invocation) throws RpcException {
- return postProcessResult(invoker.invoke(invocation), invoker, invocation);
- }
-
- @Override
- protected Result doPostProcess(Result result, Invoker<?> invoker, Invocation invocation) {
- System.out.println("Filter get the return value: " + result.getValue());
- return result;
- }
-}
-```
-
-
-### Context passing
-
-Currently, the context we are considering mainly refers to the data stored in the RpcContext. In most scenarios, the user needs to complete the passing of the Context before switching the service thread.
-
-```
-public class AsyncServiceImpl implements AsyncService {
- // Save the context of the current thread
- RpcContext context = RpcContext.getContext();
- public CompletableFuture<String> sayHello(String name) {
- return CompletableFuture.supplyAsync(() -> {
- // Set context into new thread
- RpcContext.setContext(context);
- try {
- Thread.sleep(5000);
- } catch (InterruptedException e) {
- e.printStackTrace();
- }
- return "async response from provider.";
- });
- }
-}
-```
-
-However, AsyncContext also provides the signalContextSwitch() method for a convenient Context switch.
-
-```
-public class AsyncServiceImpl implements AsyncService {
- public String sayHello(String name) {
- final AsyncContext asyncContext = RpcContext.startAsync();
- new Thread(() -> {
- asyncContext.signalContextSwitch();
- try {
- Thread.sleep(500);
- } catch (InterruptedException e) {
- e.printStackTrace();
- }
- asyncContext.write("Hello " + name + ", response from provider.");
- }).start();
- return null;
- }
-}
-```
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/blog/en-us/dubbo-protocol.md b/blog/en-us/dubbo-protocol.md
deleted file mode 100644
index 325ef5d..0000000
--- a/blog/en-us/dubbo-protocol.md
+++ /dev/null
@@ -1,182 +0,0 @@
----
-title: Introduction to the Dubbo protocol
-keywords: Dubbo, Protocol, RPC
-description: This article introduces the design of the Dubbo protocol.
----
-
-## The concept of the protocol
-The protocol is the foundation of communication between two network entities, and data is transmitted from one entity to another in the form of a byte stream over the network. In the world of byte streams, this one-dimensional byte stream cannot be reshaped into two-dimensional or multi-dimensional data structures and domain objects without a protocol.
-
-
-### What is the protocol
-The protocol is the semantics determined by both parties for the communication. For example, we design a protocol for string transmission, which allows the client to send a string and the server receives the corresponding string.
-
-This protocol is quite simple, first 4-byte represent the total length of the message, followed by 1-byte represents the length of the charset, and then followed by the message payload, charset name and string body.
-
-For example, Send a string `abc` encoded by `iso-8859-1` to the server end. After protocol trans-coding, the content is: `18 = 4 + 1 + 10 + 3|10|iso-8859-1|abc`, when the server receives these byte streams, it first reads 4-byte and converts it to int, in this case is 18, which is the length of message. Then continue to read the remaining 14 bytes, the remaining first byte read will be the length of the charset name, which is 10, the after 10-byte content is converted to a string, the co [...]
-
-In the previous example of a custom string transfer protocol, we have already seen the role of protocols in data transmission. Without a protocol, the data exchange cannot be completed. The following is Wikipedia's definition of the communication protocol.
-
-> In telecommunication, a communication protocol is a system of rules that allow two or more entities of a communications system to transmit information via any kind of variation of a physical quantity. The protocol defines the rules syntax, semantics and synchronization of communication and possible error recovery methods. Protocols may be implemented by hardware, software, or a combination of both.
-
-Communication protocols need to define syntax, semantics, and communication synchronization operations. The content described here is actually a formal description of the previous custom string transfer protocol.
-
-### The definition of `Codec`
-
-`org.apache.dubbo.remoting.Codec2` define the **Codec**'s I/O processing, so the main methods are `encode` and `decode`, as defined below:
-
-```java
-@SPI
-public interface Codec2 {
-
- @Adaptive({Constants.CODEC_KEY})
- void encode(Channel channel, ChannelBuffer buffer, Object message) throws IOException;
-
- @Adaptive({Constants.CODEC_KEY})
- Object decode(Channel channel, ChannelBuffer buffer) throws IOException;
-
-
- enum DecodeResult {
- NEED_MORE_INPUT, SKIP_SOME_INPUT
- }
-
-}
-```
-
- `Codec` works on a protocol, `encode` method means to encode the communication object to the `ByteBufferWrapper`, and `decode` method decodes the `ChannelBuffer` read from the network into `Object`, which is the communication object.
-
-
-## Common protocol mode
-Protocols in application layer have three general forms: fixed-length protocol, special delimiter protocol and protocol header + payload mode. The specific contents of these forms are described below.
-
-When reading data from the network in the form of a byte stream, it is necessary to determine when a meaningful transmission content ends. Moreover, the transmission of data on the network, there are sticky packets and fragment packets problem. The solution to this problem is that the protocol can accurately identify, when the sticky packets or fragment packets occurs, it can handle it correctly.
-
-
-### Fixed-length protocol
-
-The fixed-length protocol means that the length of the protocol content is fixed. For example, the protocol byte length is 50. When 50 bytes are read from the network, the decoding operation is performed. The fixed-length protocol is more efficient when reading or writing, because the size of the data cache is basically determined, just like an array. The defect is the lack of adaptability. Taking the RPC scene as an example, it is difficult to estimate the length.
-
-> Refer to Netty's `FixedLengthFrameDecoder`
-
-### Special delimiter protocol
-Compared to fixed-length protocols, if we can define a special character as the end of each protocol unit, we can communicate in a variable length, so as to balance the data transmission and efficiency, such as the delimiter \n.
-
-The problem with the special delimiter method is that it think about the process of protocol transmission in a simple way. For a protocol unit, it must be read all before it can be processed. In addition, it must be prevented that the data transmitted by the user cannot be the same as the delimiter, otherwise it will be disordered.
-
-> Refer to Netty's `DelimiterBasedFrameDecoder`
-
-### Variable length protocol(protocol head + payload)
-
-Generally, it is a custom protocol, which is composed of a fixed length and a variable content. The fixed length part needs to specify the length of the variable content part.
-
-```sh
-+————————————————+
-|fixed-length |
-+————————————————+
-|variable content|
-+————————————————+
-```
-
-> Refer to Netty's `LengthFieldBasedFrameDecoder`
-
-The Dubbo protocol is actually a variable length protocol, which is covered in more detail in later chapters.
-
-## The Dubbo protocol
-
-### Overview to the Dubbo protocol
-The Dubbo framework defines a proprietary RPC protocol in which the specific content of the request and response protocols is presented using a table.
-
-
-
-### Dubbo protocol details
-
-- Magic - Magic High & Magic Low (16 bits)
-
- Identify protocol version, Dubbo protocol: 0xdabb
-
-- Req/Res (1 bit)
-
- Identify a request or response. request: 1; response: 0.
-
-- 2 Way (1 bit)
-
- Only useful when Req/Res is 1(request), identifying if you expect to return a value from the server. Set to 1 if a return value from the server is required.
-
-- Event (1 bit)
-
- Identifies whether it is an event message, for example, a heartbeat event. Set to 1 if this is an event.
-
-- Serialization ID (5 bit)
-
- Identifies the serialization type: for example, the value of fastjson is 6.
-
-- Status (8 bits)
-
- Only useful when Req/Res is 0 (response), used to identify the status of the response
-
- - 20 - OK
- - 30 - CLIENT_TIMEOUT
- - 31 - SERVER_TIMEOUT
- - 40 - BAD_REQUEST
- - 50 - BAD_RESPONSE
- - 60 - SERVICE_NOT_FOUND
- - 70 - SERVICE_ERROR
- - 80 - SERVER_ERROR
- - 90 - CLIENT_ERROR
- - 100 - SERVER_THREADPOOL_EXHAUSTED_ERROR
-
-- Request ID (64 bits)
-
- Identifies the only request, the type is long.
-
-- Data Length (32 bits)
-
- The length of the serialized content (variable part), counted in bytes, the type is int.
-
-- Variable Part
-
- After being serialized by a specific serialization type (identified by the serialization ID), each part is a byte [] or byte.
-
- - If it is a request packet (Req/Res = 1), each part is:
- - Dubbo version
- - Service name
- - Service version
- - Method name
- - Method parameter types
- - Method arguments
- - Attachments
- - If it is a response packet (Req/Res = 0), each part is:
- - Return value's type (byte), identifying the type of value returned from the server:
- - Return null: RESPONSE_NULL_VALUE 2
- - Normal response value: RESPONSE_VALUE 1
- - Exception: RESPONSE_WITH_EXCEPTION 0
- - Return value: response bytes returned from the server
-
-**Note:** For the variable part, when uses json serialization in current version of Dubbo framework, an additional line break is added as a separator between each part of the content. Please add a new line break after each part of the variable part, such as:
-
-```
-Dubbo version bytes (line break)
-Service name bytes (line break)
-...
-```
-
-## Advantages and disadvantages about the Dubbo protocol
-
-### Advantages
-
-- The protocol is designed to be very compact. The data type can be represented by 1 bit will not be represented by a byte, such as a boolean type identifier.
-- The request header is the same as response header, and the specific content is assembled to the variable part through the serializer, and it is simple to implement.
-
-### To be improved
-
-- Similar to the http request, the header can determine the resource to be accessed, and Dubbo needs to involve the specific serializer to resolve the service name, method, method signature, and these resource locators are string type or string array. It's easy to convert to bytes, so it can be assembled into the header. Similar to http2 header compression, resources called for rpc can also be negotiated with an int to identify, which improves performance. This is easier to implement if [...]
-
-- Use req/res to determine if it is a request, then you can refine the protocol, remove some unwanted identifiers and add some specific identifiers. For example, `status`, `twoWay` can be strictly customized to remove redundant identifiers. There is also a timeout identifier that is transmitted as the `attachment` of the Dubbo. In theory, it should be placed in the header of the request protocol, because the timeout is essential in the network request. Referring to `attachment`, you can [...]
-
-- Dubbo will convert the service name `com.alibaba.middleware.hsf.guide.api.param.ModifyOrderPriceParam` to `Lcom/alibaba/middleware/hsf/guide/api/param/ModifyOrderPriceParam;`, which is theoretically unnecessary, simply append a `;` will be fine.
-
-- The Dubbo protocol does not reserve extension fields, and cannot add new identifiers. The scalability is not very good. For example, the only way to add the `response context` function is to change the protocol version, but this requires both the client and server versions to be upgraded. Very unfriendly in distributed scenarios.
-
-## Conclusion
-
-This article mainly introduces the concept of the protocol and the commonly used protocol mode. Then it analyzes the Dubbo protocol in detail and also mentions some shortcomings. However, compared with its simplicity and ease of implementation, the above shortcomings are not enough to drive us to redesign a new version of the protocol, so we welcome suggestions and features for protocol optimization.
diff --git a/blog/en-us/dubbo-registry-nacos-integration.md b/blog/en-us/dubbo-registry-nacos-integration.md
deleted file mode 100644
index 21051a1..0000000
--- a/blog/en-us/dubbo-registry-nacos-integration.md
+++ /dev/null
@@ -1,487 +0,0 @@
-# Dubbo Integrates with Nacos to Become a Registry
-Nacos is an important registry in Dubbo ecosystem, and dubbo-registry-nacos is the implementation of Dubbo-integrated Nacos registry.
-
-## Preparation Works
-Before you integrate dubbo-registry-nacos into your Dubbo project, make sure the Nacos service is started in the background. If you are not familiar with the basic use of Nacos, you can refer to the Quick Start for Nacos: https://nacos.io/en-us/docs/quick-start.html. Nacos versions above 0.6.1 are recommended.
-
-## Get Started Quickly
-The operation steps for Dubbo to integrate Nacos into a registry are simple, the general steps can be divided into "add Maven dependency" and "configure the registry."
-
-## Increase Maven Dependency
-First, you need to add the Maven dependency of dubbo-registry-nacos to your project's pom.xml file, and it is strongly recommended that you use Dubbo 2.6.5:
-
-```xml
-<dependencies>
-
- ...
-
- <!-- Dubbo Nacos registry dependency -->
- <dependency>
- <groupId>org.apache</groupId>
- <artifactId>dubbo-registry-nacos</artifactId>
- <version>0.0.2</version>
- </dependency>
-
- <!-- Keep latest Nacos client version -->
- <dependency>
- <groupId>org.apache.nacos</groupId>
- <artifactId>nacos-client</artifactId>
- <version>[0.6.1,)</version>
- </dependency>
-
- <!-- Dubbo dependency -->
- <dependency>
- <groupId>org.apache</groupId>
- <artifactId>dubbo</artifactId>
- <version>2.6.5</version>
- </dependency>
-
- <!-- Alibaba Spring Context extension -->
- <dependency>
- <groupId>org.apache.spring</groupId>
- <artifactId>spring-context-support</artifactId>
- <version>1.0.2</version>
- </dependency>
-
- ...
-
-</dependencies>
-```
-When you add dubbo-registry-nacos to your project, you don't need to programmatically implement the service discovery and registration logic, the actual implementation is provided by the third-party package, and then to configure the Naocs registry.
-
-## Configure the Registry
-Assuming your Dubbo application is assembled by the Spring Framework, there are two configuration options: Dubbo Spring externalization configuration and Spring XML configuration files, I strongly recommend the former.
-
-## Dubbo Spring Externalization Configuration
-Dubbo Spring externalization configuration is a new feature introduced by Dubbo 2.5.8, which automatically generates and binds Dubbo configuration Bean through the Spring Environment property, simplifying configuration and lowering the threshold for microservice development.
-
-
-Assume your Dubbo application uses Zookeeper as the registry and its server IP address is 10.20.153.10, the registered address is also stored in the dubbo-config.properties file as a Dubbo externalization configuration attribute, as shown below:
-
-```properties
-## application
-dubbo.application.name = your-dubbo-application
-
-## Zookeeper registry address
-dubbo.registry.address = zookeeper://10.20.153.10:2181
-...
-```
-
-Assuming your Nacos Server is also running on server 10.20.153.10 and using the default Nacos service port 8848, you can simply adjust the dubbo.registry.address property as follows:
-```properties
-## 其他属性保持不变
-
-## Nacos registry address
-dubbo.registry.address = nacos://10.20.153.10:8848
-...
-```
-
-Subsequently, restart your Dubbo application, and Dubbo's service delivery and consumption information can be displayed in the Nacos console:
-
-
-
-
-As shown in the figure, the service name prefixed with providers: is the meta-information for the service provider, and consumers: represents the meta-information of the service consumer. Click "Details" to view service status details:
-
-
-
-If you are using the Spring XML configuration file to assemble the Dubbo registry, refer to the next section.
-
-## Spring XML Configuration File
-
-Also, assume your Dubbo application uses Zookeeper as the registry and its server IP address is 10.20.153.10 and assemble the Spring Bean in an XML file, as shown below:
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
-
- <!-- Provider application information for dependency calculation -->
- <dubbo:application name="dubbo-provider-xml-demo" />
-
- <!-- Using the Zookeeper registry Zookeeper -->
- <dubbo:registry address="zookeeper://10.20.153.10:2181" />
- ...
-</beans>
-```
-
-Similar to the Dubbo Spring externalization configuration, simply adjust the address property configuration:
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
-
- <!-- Provider application information for dependency calculation-->
- <dubbo:application name="dubbo-provider-xml-demo" />
-
- <!-- Using the Nacos registry -->
- <dubbo:registry address="nacos://10.20.153.10:8848" />
- ...
-</beans>
-```
-
-Once you restart the Dubbo application, you can also see that the registration meta-information for both service providers and consumers is presented in the Nacos console:
-
-
-
-Do you absolutely configure or switch Nacos registry super Easy? If you want to get more or unclear, refer to the complete example below.
-
-## Complete Example
-
-The metadata in the above image is derived from the Dubbo Spring annotation-driven example and the Dubbo Spring XML configuration-driven example, both of which will be described below, you can choose your preferred programming model. Before we get into the formal discussion, let's look at the preparations for both, as they both rely on Java service interfaces and implementations. Also, ensure that the Nacos service is started in the local (127.0.0.1) environment.
-
-### Example Interfaces and Implementations
-
-First, define the sample interface, as follows:
-```java
-package org.apache.dubbo.demo.service;
-
-/**
- * DemoService
- *
- * @since 2.7.4
- */
-public interface DemoService {
-
- String sayName(String name);
-
-}
-```
-
-Provide implementation classes for the above interfaces:
-
-```java
-package org.apache.dubbo.demo.service;
-
-import org.apache.dubbo.config.annotation.Service;
-import org.apache.dubbo.rpc.RpcContext;
-
-import org.springframework.beans.factory.annotation.Value;
-
-/**
- * Default {@link DemoService}
- *
- * @since 2.7.4
- */
-@Service(version = "${demo.service.version}")
-public class DefaultService implements DemoService {
-
- @Value("${demo.service.name}")
- private String serviceName;
-
- public String sayName(String name) {
- RpcContext rpcContext = RpcContext.getContext();
- return String.format("Service [name :%s , port : %d] %s(\"%s\") : Hello,%s",
- serviceName,
- rpcContext.getLocalPort(),
- rpcContext.getMethodName(),
- name,
- name);
- }
-}
-```
-
-Once the interface and implementation are ready, the annotation-driven and XML configuration-driven implementations will be used below.
-
-## Spring Annotation-driven Example
-
-Dubbo 2.7.4 reconstructs the Spring annotation-driven programming model.
-
-### Service Provider Annotation-driven Implementation
-
-- Define property source of Dubbo provider externalization configuration - provider-config.properties
-
-```properties
-## application
-dubbo.application.name = dubbo-provider-demo
-
-## Nacos registry address
-dubbo.registry.address = nacos://127.0.0.1:8848
-
-## Dubbo Protocol
-dubbo.protocol.name = dubbo
-dubbo.protocol.port = -1
-
-# Provider @Service version
-demo.service.version=1.0.0
-demo.service.name = demoService
-```
-
-- Implement service provider bootstrap - DemoServiceProviderBootstrap
-
-```java
-package org.apache.dubbo.demo.provider;
-
-import org.apache.dubbo.config.spring.context.annotation.EnableDubbo;
-import org.apache.dubbo.demo.service.DemoService;
-
-import org.springframework.context.annotation.AnnotationConfigApplicationContext;
-import org.springframework.context.annotation.PropertySource;
-
-import java.io.IOException;
-
-/**
- * {@link DemoService} provider demo
- */
-@EnableDubbo(scanBasePackages = "org.apache.dubbo.demo.service")
-@PropertySource(value = "classpath:/provider-config.properties")
-public class DemoServiceProviderBootstrap {
-
- public static void main(String[] args) throws IOException {
- AnnotationConfigApplicationContext context = new AnnotationConfigApplicationContext();
- context.register(DemoServiceProviderBootstrap.class);
- context.refresh();
- System.out.println("DemoService provider is starting...");
- System.in.read();
- }
-}
-
-```
-
-Wherein, the annotation @EnableDubbo activates the Dubbo annotation-driven and externalization configuration, its scanBasePackages property scans the specified Java package, exposes all service interface implementation classes labeled @Service as Spring Bean, and then exports the Dubbo service.
-
-@PropertySource is the standard import property configuration resource annotation introduced by Spring Framework 3.1, which provides externalization configuration for Dubbo.
-
-## Service consumer annotation-driven implementation
-
-- Define property source of Dubbo consumer externalization configuration - consumer-config.properties
-
-```properties
-## Dubbo Application info
-dubbo.application.name = dubbo-consumer-demo
-
-## Nacos registry address
-dubbo.registry.address = nacos://127.0.0.1:8848
-
-# @Reference version
-demo.service.version= 1.0.0
-```
-
-Similarly, the dubbo.registry.address property points to the Nacos registry, through which metadata about other Dubbo services is obtained.
-
-- Implement service consumer bootstrap class - DemoServiceConsumerBootstrap
-
-```java
-package org.apache.dubbo.demo.consumer;
-
-import org.apache.dubbo.config.annotation.Reference;
-import org.apache.dubbo.config.spring.context.annotation.EnableDubbo;
-import org.apache.dubbo.demo.service.DemoService;
-
-import org.springframework.context.annotation.AnnotationConfigApplicationContext;
-import org.springframework.context.annotation.PropertySource;
-
-import javax.annotation.PostConstruct;
-import java.io.IOException;
-
-/**
- * {@link DemoService} consumer demo
- */
-@EnableDubbo
-@PropertySource(value = "classpath:/consumer-config.properties")
-public class DemoServiceConsumerBootstrap {
-
- @Reference(version = "${demo.service.version}")
- private DemoService demoService;
-
- @PostConstruct
- public void init() {
- for (int i = 0; i < 10; i++) {
- System.out.println(demoService.sayName("小马哥（mercyblitz）"));
- }
- }
-
- public static void main(String[] args) throws IOException {
- AnnotationConfigApplicationContext context = new AnnotationConfigApplicationContext();
- context.register(DemoServiceConsumerBootstrap.class);
- context.refresh();
- context.close();
- }
-}
-
-```
-
-Similarly, the @EnableDubbo annotation activates the Dubbo annotation-driven and externalization configuration, although it currently belongs to the service consumer and does not require the Java package name to scan the service implementation labeled @Service.
-
-@Reference is a dependency injection annotation for Dubbo remote services that requires service provider and consumer contract interface, version, and group information. In the current service consumption example, the service version of DemoService is derived from the property configuration file consumer-config.properties.
-
-The @PostConstruct code shows that when the DemoServiceConsumerBootstrap Bean is initialized, it executes ten Dubbo remote method invocation.
-
-### Run the Annotation-driven Example
-
-Start DemoServiceProviderBootstrap twice locally and the registry will have two health services:
-
-
-
-Run DemoServiceConsumerBootstrap again and the results are as follows:
-
-```
-Service [name :demoService , port : 20880] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :demoService , port : 20881] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :demoService , port : 20880] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :demoService , port : 20880] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :demoService , port : 20881] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :demoService , port : 20881] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :demoService , port : 20880] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :demoService , port : 20880] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :demoService , port : 20881] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :demoService , port : 20881] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-```
-
-Run correctly and the service consumer uses a load balancing strategy to allocate ten RPC calls equally to two Dubbo service provider instances.
-
-### Spring XML Configuration-driven Example
-
-Spring XML configuration-driven is the programming model of traditional Spring assembly components.
-
-#### Service Provider XML Configuration-driven
-
-Define the service provider XML context configuration file - /META-INF/spring/dubbo-provider-context.xml
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
-
- <!--
-
-Provider application information for dependency calculation
- -->
- <dubbo:application name="dubbo-provider-xml-demo"/>
-
- <!-- Using the Nacos registry -->
- <dubbo:registry address="nacos://127.0.0.1:8848"/>
-
- <!-- Using Dubbo protocol to expose services on random ports -->
- <dubbo:protocol name="dubbo" port="-1"/>
-
- <!-- Declare the service interface to be exposed -->
- <dubbo:service interface="org.apache.dubbo.demo.service.DemoService" ref="demoService" version="2.0.0"/>
-
- <!-- Implement services like local beans -->
- <bean id="demoService" class="org.apache.dubbo.demo.service.DefaultService"/>
-</beans>
-```
-
-- Implement service provider bootstrap class - DemoServiceProviderBootstrap
-
-
-```java
-package org.apache.dubbo.demo.provider;
-
-import org.apache.dubbo.demo.service.DemoService;
-
-import org.springframework.context.support.ClassPathXmlApplicationContext;
-
-import java.io.IOException;
-
-/**
- * {@link DemoService} provider demo XML bootstrap
- */
-public class DemoServiceProviderXmlBootstrap {
-
- public static void main(String[] args) throws IOException {
- ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext();
- context.setConfigLocation("/META-INF/spring/dubbo-provider-context.xml");
- context.refresh();
- System.out.println("DemoService provider (XML) is starting...");
- System.in.read();
- }
-}
-```
-
-#### Service Consumer XML Configuration-driven
-Define the consumer provider XML context configuration file - /META-INF/spring/dubbo- consumer-context.xml
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
-
- <!--
-
-Provider application information for dependency calculation
- -->
- <dubbo:application name="dubbo-consumer-xml-demo"/>
-
- <!-- Using the Nacos registry-->
- <dubbo:registry address="nacos://127.0.0.1:8848"/>
-
- <!-- Reference service interface -->
- <dubbo:reference id="demoService" interface="org.apache.dubbo.demo.service.DemoService" version="2.0.0"/>
-
-</beans>
-```
-
- - Implement service consumer bootstrap class - DemoServiceConsumerBootstrap
-
-
-```java
-package org.apache.dubbo.demo.consumer;
-
-import org.apache.dubbo.demo.service.DemoService;
-
-import org.springframework.context.support.ClassPathXmlApplicationContext;
-
-import java.io.IOException;
-
-/**
- * {@link DemoService} consumer demo XML bootstrap
- */
-public class DemoServiceConsumerXmlBootstrap {
-
- public static void main(String[] args) throws IOException {
- ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext();
- context.setConfigLocation("/META-INF/spring/dubbo-consumer-context.xml");
- context.refresh();
- System.out.println("DemoService consumer (XML) is starting...");
- DemoService demoService = context.getBean("demoService", DemoService.class);
- for (int i = 0; i < 10; i++) {
- System.out.println(demoService.sayName("小马哥（mercyblitz）"));
- }
- context.close();
- }
-}
-```
-
-#### Run XML Configuration-driven Example
-
-As such, start two DemoServiceProviderXmlBootstrap bootstraps and observe the changes in the Nacos registry service provider:
-
-
-
-The service version driven by the XML configuration is 2.0.0, so the registration service is correct.
-
-Run the service consumer bootstrap DemoServiceConsumerXmlBootstrap again and observe the console output:
-
-```
-Service [name :null , port : 20882] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :null , port : 20882] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :null , port : 20883] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :null , port : 20882] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :null , port : 20882] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :null , port : 20883] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :null , port : 20882] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :null , port : 20883] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :null , port : 20883] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-Service [name :null , port : 20883] sayName("小马哥（mercyblitz）") : Hello,小马哥（mercyblitz）
-```
-
-
-As a result, both operation and load balancing are normal due to the property demo.service.name has not been added to the current example, the "name" information is output as null. For more information, please refer to: https://github.com/apache/dubbo/tree/master/dubbo-registry/dubbo-registry-nacos.
-
-If you're interested in or fond of open source projects like Dubbo and Nacos, try clicking "star" to support them. The links are as follows:
-
-- Apache Dubbo: https://github.com/apache/dubbo
-- Dubbo Nacos Registry: https://github.com/apache/dubbo/tree/master/dubbo-registry/dubbo-registry-nacos
-- Alibaba Nacos: https://github.com/alibaba/nacos
-
diff --git a/blog/en-us/dubbo-zk.md b/blog/en-us/dubbo-zk.md
deleted file mode 100644
index 768648c..0000000
--- a/blog/en-us/dubbo-zk.md
+++ /dev/null
@@ -1,341 +0,0 @@
----
-title: Using Zookeeper in Dubbo
-keywords: Dubbo, registry center, Zookeeper, ZK
-description: This article introduces basic concepts of Zookeeper, and how to use Zookeeper as a registry center.
----
-
-# Using Zookeeper in Dubbo
-
-## Introduction of Zookeeper
-
-### The basic concept
-
-In the mordern distrbuted applications, there are multiple coordination problems between nodes and nodes, including: leader election, group service, locking, configuration management, naming and synchronization. Apache Zookeeper, as its name implied, is a distributed, open-source coordination service framwork to address these demand.
-
-In order to ensure the high performance, highly available and strictly ordered access, the performance aspects of ZooKeeper means it can be used in large, distributed systems and can also be deployed in cluster mode, which called 'ZooKeeper ensemble'. In ZooKeeper ensemble, all write requests from clients are forwarded to a single server, called the leader, through the ZAB(Zookeeper Atomic Broadcast Protocol) to make sure the message in each nodes are same. Clients can access any one of [...]
-
-
-
-*Image Credit : ebook -Zookeeper-Distributed Process Coordination from O'Reilly*
-
-The method to store the data in Zookeeper is similar as the standard UNIX file system, as a data model styled after the familiar directory tree structure of file systems. When we talking about ZooKeeper data nodes, we call it Znodes to clarify it.
-
-
-*Image Credit : ebook -Zookeeper-Distributed Process Coordination from O'Reilly*
-
-### Basic Implementation
-
-You could donwload and install Zookeeper directly[^2].
-Or you could use Homebrew [^3] `brew install zookeeper` to install Zookeeper in Mac OS.
-Considering the versatility, we run the Zookeeper by using docker in this blog. If you have not installed the docker yet, please prepare the docker environment first. [^4]
-
-#### 1. Running the Zookeeper
-
-Execute the command to run zookeeper in a docker container
-
-```shell
-docker run --rm --name zookeeper -p 2181:2181 zookeeper
-```
-
-#### 2. Entering the zookeeper container
-
-```shell
-docker exec -it zookeeper bash
-```
-
-In the `bin` directory, there is a command to start zookeeper `zkServer` and the Management Console `zkCli`
-
-```shell
-bash-4.4# ls -l bin
-total 36
--rwxr-xr-x 1 zookeepe zookeepe 232 Mar 27 04:32 README.txt
--rwxr-xr-x 1 zookeepe zookeepe 1937 Mar 27 04:32 zkCleanup.sh
--rwxr-xr-x 1 zookeepe zookeepe 1056 Mar 27 04:32 zkCli.cmd
--rwxr-xr-x 1 zookeepe zookeepe 1534 Mar 27 04:32 zkCli.sh
--rwxr-xr-x 1 zookeepe zookeepe 1759 Mar 27 04:32 zkEnv.cmd
--rwxr-xr-x 1 zookeepe zookeepe 2696 Mar 27 04:32 zkEnv.sh
--rwxr-xr-x 1 zookeepe zookeepe 1089 Mar 27 04:32 zkServer.cmd
--rwxr-xr-x 1 zookeepe zookeepe 6773 Mar 27 04:32 zkServer.sh
-```
-
-#### 3. Entering the zookeeper management interface via zkCli
-
-Since it was started through docker, the process of Zookeeper has been started and will provide the services to the public via port 2181.
-
-```shell
-bash-4.4# ps
-PID USER TIME COMMAND
- 1 zookeepe 0:02 /usr/lib/jvm/java-1.8-openjdk/jre/bin/java -Dzookeeper.log.dir=. -Dzookeeper.root
- 32 root 0:00 bash
- 42 root 0:00 ps
-```
-
-So, it allows you to access Zookeeper's console directly through `zkCli ` for management.
-
-```shell
-bash-4.4# bin/zkCli.sh -server 127.0.0.1:2181
-Connecting to 127.0.0.1:2181
-...
-WATCHER::
-
-WatchedEvent state:SyncConnected type:None path:null
-
-[zk: 127.0.0.1:2181(CONNECTED) 0] help
-ZooKeeper -server host:port cmd args
- stat path [watch]
- set path data [version]
- ls path [watch]
- delquota [-n|-b] path
- ls2 path [watch]
- setAcl path acl
- setquota -n|-b val path
- history
- redo cmdno
- printwatches on|off
- delete path [version]
- sync path
- listquota path
- rmr path
- get path [watch]
- create [-s] [-e] path data acl
- addauth scheme auth
- quit
- getAcl path
- close
- connect host:port
-```
-
-#### 4. Basic Examples on zkCli
-
-Create `/hello-zone` node:
-```shell
-[zk: 127.0.0.1:2181(CONNECTED) 19] create /hello-zone 'world'
-Created /hello-zone
-```
-
-List the child nodes under `/` and confirm that `hello-zone` is created:
-
-```shell
-[zk: 127.0.0.1:2181(CONNECTED) 20] ls /
-[zookeeper, hello-zone]
-```
-
-List the child nodes for `/hello-zone` and verify that it is empty:
-
-```shell
-[zk: 127.0.0.1:2181(CONNECTED) 21] ls /hello-zone
-[]
-```
-
-Get the data stored on the `/hello-zone` node:
-
-```shell
-[zk: 127.0.0.1:2181(CONNECTED) 22] get /hello-zone
-world
-```
-
-## Using Zookeeper in Dubbo
-Zookeeper is used for service registration discovery and configuration management in Dubbo, and the structure of data in Zookeeper is shown in the following figure:
-
-
-
-First, all data related to Dubbo is organized under the root node of `/dubbo`.
-
-The secondary directory is the service name like `com.foo.BarService`.
-
-The three-level directory has two child nodes, `providers` and `consumers`, representing the supplier and customers of the service.
-
-The URL information for each application instance associated with the service will be recorded by the Level 4 directory. The `providers` and `consumer` will stored the providers information and the consumers information of the services seperately.
-For example, the service provider of `com.foo.BarService` will register its URL Information to `/dubbo/com.foo.BarService/providers`; Similarly, service consumers will register their information under the corresponding `consumer` node. At the same time, consumers will subscribe to the corresponding `providers` node to be able to detect the changes of the service provider address list.
-
-### Prepare the sample code
-
-The code in this document can be found in https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-zookeeper.
-
-#### 1. Interface definition
-
-Define a simple `greetingservice` interface with only one simple method named `sayHello` to greet to the caller.
-
-```java
-public interface GreetingService {
- String sayHello(String name);
-}
-```
-
-#### 2. Server: Implementation
-
-Implement the `GreetingService` interface and mark it as a service for Dubbo via `@Service`.
-
-```java
-@Service
-public class AnnotatedGreetingService implements GreetingService {
- public String sayHello(String name) {
- return "hello, " + name;
- }
-}
-```
-
-#### 3. Server: Assembly
-
-Define ProviderConfiguration to assemble Dubbo services.
-
-```java
-@Configuration
-@EnableDubbo(scanBasePackages = "com.alibaba.dubbo.samples.impl")
-@PropertySource("classpath:/spring/dubbo-provider.properties")
-static class ProviderConfiguration {}
-```
-
-Dubbo-provider.properties is an external configuration in a spring application, as follows:
-
-```properties
-dubbo.application.name=demo-provider
-dubbo.registry.address=zookeeper://$DOCKER_HOST:2181
-dubbo.protocol.name=dubbo
-dubbo.protocol.port=20880
-```
-
-Since zookeeper runs in a docker container, please be noted that:
-
-* We assumes that Dubbo applications is running on the host machine (outside the docker container) in this document, and needs to replace the PATH of Zookeeper with the IP address of the Environment Variable *${DOCKER_HOST}*. Please find more detail in the official Docker documentation.
-* When the Dubbo application is a docker application, the container's name is equivalent to Zookeeper's. The container's name is ** zookeeper ** in this document.
-* Of course, if you don't want to run the Zookeeper in a container mode, just simply replace *$DOCKER_HOST* with **localhost**.
-
-#### 4. Server: Starting Service
-
-In the `main` method, you could provide the Dubbo service by running a Spring Context.
-
-
-```java
-public class ProviderBootstrap {
- public static void main(String[] args) throws Exception {
- AnnotationConfigApplicationContext context = new AnnotationConfigApplicationContext(ProviderConfiguration.class);
- context.start();
- System.in.read();
- }
-}
-```
-
-Start the `main` method of server, you will get the following output, which represents the success of the server's startup, and the `GreetingService` service is registered on the ZookeeperRegistry:
-
-```sh
-[03/08/18 10:50:33:033 CST] main INFO zookeeper.ZookeeperRegistry: [DUBBO] Register: dubbo://192.168.99.1:20880/com.alibaba.dubbo.samples.api.GreetingService?anyhost=true&application=demo-provider&dubbo=2.6.2&generic=false&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=12938&side=provider×tamp=1533264631849, dubbo version: 2.6.2, current host: 192.168.99.1
-```
-
-You could find the registration information of the service provider through the Zookeeper management terminal:
-
-```sh
-$ docker exec -it zookeeper bash
-bash-4.4# bin/zkCli.sh -server localhost:218
-Connecting to localhost:2181
-...
-Welcome to ZooKeeper!
-JLine support is enabled
-...
-[zk: localhost:2181(CONNECTED) 0] ls /dubbo/com.alibaba.dubbo.samples.api.GreetingService/providers
-[dubbo%3A%2F%2F192.168.99.1%3A20880%2Fcom.alibaba.dubbo.samples.api.GreetingService%3Fanyhost%3Dtrue%26application%3Ddemo-provider%26dubbo%3D2.6.2%26generic%3Dfalse%26interface%3Dcom.alibaba.dubbo.samples.api.GreetingService%26methods%3DsayHello%26pid%3D12938%26side%3Dprovider%26timestamp%3D1533264631849]
-```
-You could find that the Dubbo services just registered its URL address at the `providers` node as follows:
-*dubbo://192.168.99.1:20880/com.alibaba.dubbo.samples.api.GreetingService?anyhost=true&application=demo-provider&dubbo=2.6.2&generic=false&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=12938&side=provider×tamp=1533264631849*
-
-
-#### 5. Client: Reference Service
-You could declare the reference service by @Reference, while it will generate a full call. The target address of the service could be queried by the Zookeeper's `provider` node.
-
-```java
-@Component("annotatedConsumer")
-public class GreetingServiceConsumer {
- @Reference
- private GreetingService greetingService;
-
- public String doSayHello(String name) {
- return greetingService.sayHello(name);
- }
-}
-```
-
-#### 6. Client: Assembling
-Define the ConsumerConfiguration to assemble Dubbo service.
-
-```java
-@Configuration
-@EnableDubbo(scanBasePackages = "com.alibaba.dubbo.samples.action")
-@PropertySource("classpath:/spring/dubbo-consumer.properties")
-@ComponentScan(value = {"com.alibaba.dubbo.samples.action"})
-static class ConsumerConfiguration {}
-```
-"dubbo-consumer.properties" is a method of external configuration in a Spring application, as follows:
-
-```properties
-dubbo.application.name=demo-consumer
-dubbo.registry.address=zookeeper://$DOCKER_HOST:2181
-dubbo.consumer.timeout=3000
-```
-
-Same as **3. Server: Assembling**, You need to modify *$DOCKER_HOST* defined in *dubbo.registry.address* according to your own environment. You could find more instructions in step 3.
-
-
-#### 7. Client: Initiating A Remote Call
-Run `main` to initiate a remote call from a existed service provider. Dubbo first subscribes to the zookeeper service address and then selects one from the list of returned addresses to invoke the client:
-
-```java
-public class ConsumerBootstrap {
- public static void main(String[] args) {
-public class ConsumerBootstrap {
-
- public static void main(String[] args) throws IOException {
- AnnotationConfigApplicationContext context = new AnnotationConfigApplicationContext(ConsumerConfiguration.class);
- context.start();
- GreetingServiceConsumer greetingServiceConsumer = context.getBean(GreetingServiceConsumer.class);
- String hello = greetingServiceConsumer.doSayHello("zookeeper");
- System.out.println("result: " + hello);
- System.in.read();
- }
-}
-```
-
-The output are as follows:
-
-```shell
-[03/08/18 01:42:31:031 CST] main INFO zookeeper.ZookeeperRegistry: [DUBBO] Register: consumer://192.168.99.1/com.alibaba.dubbo.samples.api.GreetingService?application=demo-consumer&category=consumers&check=false&default.timeout=3000&dubbo=2.6.2&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=82406&side=consumer×tamp=1533274951195, dubbo version: 2.6.2, current host: 192.168.99.1 #1
-[03/08/18 01:42:31:031 CST] main INFO zookeeper.ZookeeperRegistry: [DUBBO] Subscribe: consumer://192.168.99.1/com.alibaba.dubbo.samples.api.GreetingService?application=demo-consumer&category=providers,configurators,routers&default.timeout=3000&dubbo=2.6.2&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=82406&side=consumer×tamp=1533274951195, dubbo version: 2.6.2, current host: 192.168.99.1 #2
-...
-result: hello, zookeeper
-```
-
-Description:
-
-1. **Register**: consumer://192.168.99.1/...&**category=consumers**&： In Zookeeper, consumers could register their information and store it at the `consumers` node
-2. **Subscribe**: consumer://192.168.99.1/...&**category=providers,configurators,routers**&：Consumers subscribe `providers`, `configurators`, `routers` from Zookeepers. The `configurations` is related to the Dubbo configuration, and `routers` is related to routing rules. The providers node subscription should be noted. When a new service provider to join, due to the relationship between the subscription, the new address list will be pushed to the subscriber. So service consumers also dyn [...]
-
-You could find the registration information of the service provider through the Zookeeper management terminal:
-```sh
-$ docker exec -it zookeeper bash
-bash-4.4# bin/zkCli.sh -server localhost:218
-Connecting to localhost:2181
-...
-Welcome to ZooKeeper!
-JLine support is enabled
-...
-[zk: localhost:2181(CONNECTED) 4] ls /dubbo/com.alibaba.dubbo.samples.api.GreetingService/consumers
-[consumer%3A%2F%2F192.168.99.1%2Fcom.alibaba.dubbo.samples.api.GreetingService%3Fapplication%3Ddemo-consumer%26category%3Dconsumers%26check%3Dfalse%26default.timeout%3D3000%26dubbo%3D2.6.2%26interface%3Dcom.alibaba.dubbo.samples.api.GreetingService%26methods%3DsayHello%26pid%3D82406%26side%3Dconsumer%26timestamp%3D1533274951195]
-```
-
-You could see that consumers of Dubbo's servicehas registered its URL address at the `consumers` node:
-
-*consumer://192.168.99.1/com.alibaba.dubbo.samples.api.GreetingService?application=demo-consumer&category=providers,configurators,routers&default.timeout=3000&dubbo=2.6.2&interface=com.alibaba.dubbo.samples.api.GreetingService&methods=sayHello&pid=82406&side=consumer×tamp=1533274951195*
-
-
-## Summary
-This document focuses on how to use ZooKeeper as a registry in Dubbo. This document also mentioned that the Zookeeper could be a configuration center and a service management in Dubbo. Zookeeper is a single-node, standalone mode. However, developers always bulid a Zookeeper server cluster called * Zookeeper ensemble * in the real world.
-
-Through this document, readers can learn:
-* Basic concepts and applications of ZooKeeper
-* The function of Zookeeper in Dubbo application
-* Learn about Zookeeper's interaction through practical sample codes
-* The storage of service registration and consumption information of Dubbo with ZooKeeper
-
-[^1]: https://www.ixiacom.com/company/blog/apache-zab—zookeeper-atomic-broadcast-protocol
-[^2]: https://www.apache.org/dyn/closer.cgi/zookeeper/
-[^3]: https://brew.sh
-[^4]: https://www.docker.com/community-edition
diff --git a/blog/en-us/dubbo2-js.md b/blog/en-us/dubbo2-js.md
deleted file mode 100644
index 5f012e6..0000000
--- a/blog/en-us/dubbo2-js.md
+++ /dev/null
@@ -1,274 +0,0 @@
----
-title: Implementation of cross-language calls by Dubbo2.js
-keywords: Dubbo, Cross-language, Node, NodeJS, js
-description: This article introduces how to use Dubbo.js to implement cross-language calls.
----
-
-
-# Implementation of cross-language calls by Dubbo2.js
-
-> [dubbo2.js](https://github.com/dubbo/dubbo2.js) is a Dubbo client for node.js developped by [Qianmiwang](https://www.qianmi.com/). It supports Dubbo's native protocol, which makes the RPC calls between javascript and java efficient and agile. This tool has been contributed to Dubbo's community.
-
-## Cross-language calls for micro service
-
-Nowadays, Internet architecture tends to be micro-service way. The discussions about micro-service architecture becomes the most mentioned topic in different technical conferences. In China, most of the companies, such as Qianmiwang, choose Dubbo as their micro-servie architecture solution. As most of the internet companies, Qianmiwang uses various of programming languages. Java is for most of the backend services. Each business based on these backend can choose its own programming langu [...]
-
- - Spring cloud. Spring cloud provides a set of components for micro-service development. It is based on HTTP protocol and is designed in the restful way, which makes it support cross-language calls. Other languages can call the services simply by implementing an HTTP interface.
- - Service mesh. People call service mesh the next generation of micro-service framework. The core of this solution is SideCar. Even though the concept of SideCar changes a lot during the revolution of Service mesh, its main job never changed: providing reliable communication between different services.
- - Motan. [Motan](https://github.com/weibocom/motan) is an open source cross-language service framework developped by Sina Weibo. Its early version only supports motan-java. However, as the new versions come out, more languages are supported in order to handle the cross-language problem. Its newest version(1.1.0) provides motan-go, motan-php, motan-openresty, etc. Similar to SideCar in Service mesh, Motan forwards messages by mortan-go, which can be considered as an agent. Meanwhile, mo [...]
-
- According to the solutions below, there are two ways to solve the cross-language calls problem:
-
- - communicating by a common protocol.
- - implementing an agent as a protocol adapter.
-
- When a new team is choosing technical solutions, what I mentioned below could be our candidates. Meanwhile, the old system's compatibility and migration costs should also be considered. The first trial we did is to work on RPC protocol.
-
-## Cross-language calls by a common protocol
-
- ### SpringMVC
-
- 
-
- Before achieving the real cross-language calls, the most common solution is to use the http protocol. We can call Dubbo provider indirectly by controller/restController provided by springmvc. This is easy to carry out, but there are lots of inconveniences. firstly, a call will go through too many nodes. Secondly, an extra communication layer (for http protocol) will be involved, but it could have been handled simply by the TCP protocol. Thirdly, we need to implement the RPC interface i [...]
-
- ### We support some common protocols
-
- Most of the service management frameworks support multiple protocols, dubbo as well. Besides its own protocol, the common protocols such as Dangdangwang's [Rest](https://dangdangdotcom.github.io/dubbox/rest.html) protocol and Qianmiwang's [json-rpc](https://github.com/apache/dubbo-rpc-jsonrpc) protocol are also supported.
-
- The developers getting used to traditional RPC interfaces might feel uncomfortable while working on restful RPC interfaces. On the one hand, this is not good for rebuilding new interfaces. On the other hand, restful style might make these interfaces incompatible with the other protocols used by old interfaces. Of course, if there is no old system problems, using Rest protocol is the easiest implementation of cross-language calls, since most of the languages support it.
-
- Even if Dubbo has tried on restful interface, the difference between rest architecture and RPC architecture should not be ignored. Rest architecture defines each resources, and it needs basic operations of http protocols such as GET, POST, DELETE, PUT. In my opinion, a Rest protocol is more for calls between different systems on the internet, while RPC is suitable for inner system calls. Similar to Rest protocol, json-rpc is also implemented by text sequence and http protocol. Using js [...]
-
- Json-rpc is Qianmiwang's early solution for cross-language protocol. They open-sourced their [dubbo-client-py](https://github.com/dubbo/dubbo-client-py) and [dubbo-node-client](https://github.com/QianmiOpen/dubbo-node-client), two clients based on json-rpc protocol. With these tools, we can easily call the rpc services provided by dubbo-provider-java with while using python or node.js. The inner system calls for java services are still mainly implemented by Dubbo protocol. In addition, [...]
-
- ``` xml
- <dubbo:protocol name="dubbo" port="20880" />
- <dubbo:protocol name="jsonrpc" port="8080" />
- ```
-
-### Customized Protocols for Cross-language Support
-
-The so-called protocol of the microservice framework can be simply interpreted as: message format and serialization scheme. Generally, the service governance framework would provide numbers of protocol configuration items for users to choose from. In addition to the above two common protocols,there exists some other customized protocols like the dubbo protocol, the default protocol for the dubbo framework, and Motan2, a cross-language protocol provided by the motan framework.
-
-#### Motan2 for cross-language support
-
-
-
-
-
-In the original Motan protocol, the protocol message consisted only of the Header and the Body, making deserialization indispensable for acquiring data stored in the Body, like path, param and group, which is terribly unfriendly for cross-language support. Therefore, the content of the protocol was modifiedin Motan2, Weibo released the open-source projects, [motan-go](https://github.com/weibocom/motan-go/), [motan-php](https://github.com/weibocom/motan-php) and [motan-openresty](https:// [...]
-
-
-
-
-
-
-After observation we find out that there is no big difference between the configuration of Motan2 and the dual protocol. It’s just that the agent here is implicit, and it co-exists with the main service. The most obvious difference is that different languages do not interact directly in agent scheme.
-
-#### Dubbo for cross-language support
-
-Instead of cross-language support, the dubbo protocol was originally designed only for common rpc requests. However, it’s not always the case that we can only choose to support it or not. We can always choose to offer different levels of support. It may be hard to offer cross-language support based on the dubbo protocol, but not impossible. Actually, Qianmiwang succeeded. It conquered the front-end cross-language business field built by nodejs with dubbo2.js. It builds the bridge between [...]
-
-##### Dubbo protocol message format:
-
-
-
-
-
-Details in dubbo protocol header message:
-
-- Magic: similar to magic number in Java bytes code files, which is used to determine whether it is a data pack of dubbo protocol. The magic number is the constant, 0xdabb.
-- Flag: contains 8 bits. The lower four bits are used to indicate the type of serialization tool used for message body data (default hessian). Among the upper four bits, the 1 at first bit indicates request, the 1 at second bit indicates dual transfer, 1 at third bits indicates the heartbeat.
-- Status: used toset response status. Dubbo defines some types for response. Details can be found in <span data-type="color" style="color:rgb(36, 41, 46)"><span data-type="background" style="background-color:rgba(27, 31, 35, 0.05)">com.alibaba.dubbo.remoting.exchange.Response</span></span>
-- Invoke id: Message id,Type long, Unique indentifier for each request (Due to asynchronous communication, it is used to match the request to the corresponding returned response)
-- Body length: message body length, type int,record bytes of body content.
-- Body content: request param, where serializedresponse parameters are stored.
-
-Protocol messages will eventually become bytes and be transmitted using TCP. Any language that supports network modules and has a socket will be able to be communicatedwith. Then, why cross-language support is difficult? There are two main obstaclesin calling service in Java using other languages:
-
-1. <span data-type="color" style="color:#24292E">How </span><span data-type="color" style="color:#212121">can different languages represent data types in java, especially dynamiclanguages with possible non-strict data types</span>?
-2. <span data-type="color" style="color:#24292E">How to serialize string across language?</span>
-
-## How does dubbo2.js solve problems?
-
-
-We have analyzed two obstacles above. The key to dubbo2.js in solving these two problems depends on two class libraries: [js-to-java](https://github.com/node-modules/js-to-java)，[hessian.js](https://github.com/node-modules/hessian.js). js-to-java, which makes nodejs have the ability to express Java objects. Hessian.js provides serialization capabilities. With the help of nodejs socket, and a duplicate set of dubbo protocol message format, we can finally achieve nodejs call to java-dubbo [...]
-
-
-## Quick Start
-
-
-To give an intuitive feeling to readers interested in dubbo2.js, this section presents a quick start example that shows how easy it is to call dubbo service using dubbo2.js.
-
-### 1. Initiate dubbo-java-provider
-Java provides the backend dubbo service. Firstly, let’s define the service interface:
-```java
-public interface DemoProvider {
- String sayHello(String name);
- String echo() ;
- void test();
- UserResponse getUserInfo(UserRequest request);
-}
-```
-
-Then we implement the interface:
-```java
-public class DemoProviderImpl implements DemoProvider {
- public String sayHello(String name) {
- System.out.println("[" + new SimpleDateFormat("HH:mm:ss").format(new Date()) + "] Hello " + name + ", request from consumer: " + RpcContext.getContext().getRemoteAddress());
- return "Hello " + name + ", response form provider: " + RpcContext.getContext().getLocalAddress();
- }
- @Override
- public String echo() {
- System.out.println("receive....");
- return "pang";
- }
- @Override
- public void test() {
- System.out.println("test");
- }
- @Override
- public UserResponse getUserInfo(UserRequest request) {
- System.out.println(request);
- UserResponse response = new UserResponse();
- response.setStatus("ok");
- Map<String, String> map = new HashMap<String, String>();
- map.put("id", "1");
- map.put("name", "test");
- response.setInfo(map);
- return response;
- }
-}
-```
-
-After that,<span data-type="color" style="color:#24292E"> we expose the dubbo service with xml files:</span>
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://code.alibabatech.com/schema/dubbo"
- xmlns="http://www.springframework.org/schema/beans"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
- http://code.alibabatech.com/schema/dubbo http://code.alibabatech.com/schema/dubbo/dubbo.xsd">
-
- <!-- dubbo provider info, used to compute dependency -->
- <dubbo:application name="demo-provider"/>
-
- <dubbo:registry protocol="zookeeper" address="localhost:2181"/>
-
- <!-- dubbo protocol, used to expose service at port 20880 -->
- <dubbo:protocol name="dubbo" port="20880"/>
-
- <!-- realize a service as a local bean -->
- <bean id="demoProvider" class="com.alibaba.dubbo.demo.provider.DemoProviderImpl"/>
-
- <!-- claim for service interfaces to expose -->
- <dubbo:service interface="com.alibaba.dubbo.demo.DemoProvider" ref="demoProvider" version="1.0.0"/>
-
-</beans>
-```
-
-After we implemented all the configurations on server side, initiate an object initiater to register a dubbo service locally:
-
-```java
-public class Provider {
- public static void main(String[] args) throws Exception {
- ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[]{"META-INF/spring/dubbo-demo-provider.xml"});
- context.start();
- System.in.read();
- }
-}
-```
-
-### 2. Implement dubbo client-side for nodejs
-Install dubbo2.js using npm:
-```sh
-npm install dubbo2.js --save
-```
-
-Configure dubboConfig.ts:
-```typescript
-import { Dubbo, java, TDubboCallResult } from 'dubbo2.js'
-
-const dubbo = new Dubbo({
- application: {name: 'demo-provider'},
- register: 'localhost:2181',
- dubboVersion: '2.0.0',
- interfaces: [
- 'com.alibaba.dubbo.demo.DemoProvider',
- ],
-});
-
-interface IDemoService {
- sayHello(name: string): TDubboCallResult<string>;
-}
-
-export const demoService = dubbo.proxyService<IDemoService>({
- dubboInterface: 'com.alibaba.dubbo.demo.DemoProvider',
- version: '1.0.0',
- methods: {
- sayHello(name: string) {
- return [java.String(name)];
- },
-
- echo() {},
-
- test() {},
-
- getUserInfo() {
- return [
- java.combine('com.alibaba.dubbo.demo.UserRequest', {
- id: 1,
- name: 'nodejs',
- email: 'node@qianmi.com',
- }),
- ];
- },
- },
-});
-```
-
-> Using typescript brings better coding experience.
-
-Implement caller class main.ts：
-
-```typescript
-import {demoService} from './dubboConfig'
-
-demoService.sayHello('kirito').then(({res,err})=>{
- console.log(res)
-});
-```
-
-### 3. Call main.ts:
-
-Run nodejs client in Debug mode:
-
-```sh
-DEBUG=dubbo* ts-node main.ts
-```
-
-Checkout running results:
-
-```sh
-Hello kirito, response form provider: 172.19.6.151:20880
-```
-
-Congratulations！
-
-## Features
-
-
-- Support zookeeper as register center
-- Support TCP Dubbo Native protocol
-- Support directly Dubbo connection
-- Support link tracing
-- Generate dubbo interface Automatically
-
-## More details
-
-The sample code in this article is available here, [https://github.com/dubbo/dubbo2.js](https://github.com/dubbo/dubbo2.js).
-If you don't know much about the dubbo protocol and want to understand how it works, the project provides a sub-moudle: java-socket-consumer, which is implemented in a process-oriented approach, realizing a process of sending dubbo protocal message with native socket and making function calls, and then get response.
-
-
diff --git a/blog/en-us/dubboAsync_client.md b/blog/en-us/dubboAsync_client.md
deleted file mode 100644
index d5993be..0000000
--- a/blog/en-us/dubboAsync_client.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Implementation background and practice of Dubbo client asynchronous interface
-keywords: Dubbo, Asynchronous, Reactive
-description: Implementation background and practice of Dubbo client asynchronous interface
----
-
-# Implementation background and practice of Dubbo client asynchronous interface
-
-## Preface
-
-
-
-Let's start with a brief introduction about the stages of a complete Dubbo invocation.
-1. Biz~ represents business thread, that is, the thread where the business logic is located. Biz~ thread pool may be created and maintained by business itself, most of which may be managed by system framework itself (for example, a web system runs under Tomcat container, Biz~ thread is maintained by Tomcat); IO~ stands for network data processing thread, which is created and maintained by IO framework (such as Netty, Grizzly). Dubbo Remoting's default Netty implementation is NioEventloop [...]
-
-2. As we all know, the way of data communication between threads is shared variables. The data communication between Biz and IO is Queue. Specifically to Dubbo, Biz put a task in EventLoop's LinkedBlockingQueue in the client side implementation (i.e. the steps labeled in Figure 1 above), and the corresponding Thread in the EventLoop will keep iteration the Queue to keep on executing the information the task contains. Specific code can refer to SingleThreadEventExecutor (by the way, the d [...]
-
-3. As shown in the figure above, a standard RPC call passes through four message (event) transfers of 1,2,3,4, respectively are the client business thread sending requests to the client IO thread, the server business logic thread receiving the server IO thread requests, the server logic thread responding to the server IO thread after processing, and the client IO thread receiving the results feedback to the business logic thread.
-
-## Client Asynchronization
-
-### Background
-In the Java language (other languages are not clear), a call of the local interface can be transparently converted into the call of remote RPC through the proxy mechanism. Most business parties prefer this programming method similar to the local interface to do remote service invocation. Therefore, although RPC is naturally asynchronous internally, users using Dubbo mostly use synchronization, while asynchrony becomes a minority use scenario. The advantage of synchronization is that the [...]
-
-Therefore, the motivation of client asynchronization is to save thread resource overhead at the cost of understanding how asynchronization is used. In the synchronous mode, the return type of API interface represents a certain business class, while in the asynchronous case, the response and the request are completely independent events, so it is most suitable for the return type of API interface to be CompletionStage mentioned above, which is the inevitable asynchronization supported by [...]
-
-The example blow is to illustrate it.
-
-### The sample
-
-Refer to the example code for event notification: [https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-notify](https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-notify)
-
-Event notification allows the Consumer to trigger 'oninvoke', 'onreturn' and 'onthrow' events, which respectively represent before the call, after the call returns normally, or when an exception occurs.
-
-You can specify a method for notifying events when configuring the Consumer, such as:
-
-```xml
-<bean id="demoCallback" class="com.alibaba.dubbo.samples.notify.impl.NotifyImpl" />
-
-<dubbo:reference id="demoService" check="false" interface="com.alibaba.dubbo.samples.notify.api.DemoService" version="1.0.0" group="cn">
- <dubbo:method name="sayHello" onreturn="demoCallback.onreturn" onthrow="demoCallback.onthrow"/>
-</dubbo:reference>
-```
-
-The code for NotifyImpl is as follows:
-
-```java
-public class NotifyImpl implements Notify{
-
- public Map<Integer, String> ret = new HashMap<Integer, String>();
-
- public void onreturn(String name, int id) {
- ret.put(id, name);
- System.out.println("onreturn: " + name);
- }
-
- public void onthrow(Throwable ex, String name, int id) {
- System.out.println("onthrow: " + name);
- }
-}
-```
-
-It is important to note that the parameters for the three methods in the custom Notify interface are as follows:
-
-* `oninvoke` The parameters of the method are the same as those of the calling method.
-* `onreturn` The first parameter of the method is the return value of the calling method, and the rest is the parameters of the calling method.
-* `onthrow` The first parameter to the method is the call exception, and the rest is the parameter to the calling method.
-
-In the above configuration, the `sayHello` method is called synchronously, so the execution of the event notification method is also synchronously executed. `async=true` can be configured to make the method call asynchronous, and the notification event method is also executed asynchronously. In particular, the `oninvoke` method executes synchronously, regardless of whether it is invoked asynchronously or not.
-
-### Practical advice
-
-* <div data-type="alignment" data-value="justify" style="text-align:justify">
- <div data-type="p">Logical Non-Strongly dependent results after RPC invocation: Asynchronous callbacks are suitable for client-side asynchronous invocation when the client <strong>is not strongly dependent on the server response</strong>.</div>
- </div>
-
-* <div data-type="alignment" data-value="justify" style="text-align:justify">
- <div data-type="p">RX scenario: after learning about reactive programming model, I believe that as long as the programming thinking can embrace reactive and the state machine design of business model can be adjusted appropriately, asynchronous solutions can be applied in all scenarios, so as to achieve better terminal response experience. For Dubbo, the current asynchronous interface model needs to be improved like the reactive model interface in order to make the user more naturally a [...]
- </div>
-
-
-### Conclusions
-
-* The motivation of client asynchronization is that the request sending and response processing are two different independent events, how the response is handled and in which thread is handled are not required to be coupled with the business logic thread of the request sending event.
-* The processing logic of response event callbacks in which thread to process is to be selected according to the situation. It is recommended that if the callback logic is relatively simple, it should be directly in the IO thread; if it contains IO type synchronization operations such as remote access or DB access, it is recommended that it be processed in a separate thread pool.
\ No newline at end of file
diff --git a/blog/en-us/dubboAsync_server.md b/blog/en-us/dubboAsync_server.md
deleted file mode 100644
index 8284cf2..0000000
--- a/blog/en-us/dubboAsync_server.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: Implementation background and practice of Dubbo server asynchronous interface
-keywords: Dubbo, Asynchrony, Reactive
-description: Implementation background and practice of Dubbo server asynchronous interface
----
-
-# Implementation background and practice of Dubbo server asynchronous interface
-
-## Preface
-It is suggested to make an understanding of the thread phase involved in the process of Dubbo first, please refer to [Implementation background and practice of Dubbo client asynchronous interface](http://dubbo.apache.org/en-us/blog/dubboAsync_client.html) for details.
-
-## Implementation background
-It is necessary to introduce the server-side thread strategy in more detail to deepen the user's judgment basis for selecting server-side asynchrony. It is also necessary to introduce coroutines, the "secret weapon" often used in server-side asynchrony.
-
-### Server-side thread strategy
-Dubbo supports a variety of NIO frameworks to implement remoting protocols. Whether Netty, Mina or Grizzly, the implementations are much the same. They are all based on event-driven methods to establish network channels and read data streams. Taking introduction to [Thread Strategy](https://javaee.github.io/grizzly/iostrategies.html) of Grizzly as an example, the following four categories are usually supported. Dubbo as an RPC framework, the default choice is the first strategy. Because [...]
-1. __Worker-thread Strategy__
-
-The most useful IOStrategy, where Selector thread delegates NIO events processing to a worker threads.
-
-
-
-
-
-
-This IOStrategy is very scalable and safe. We can change the size of selector and worker thread pool as required and there is no risk that some problem, which may occur during the specific NIO event processing, will impact other Channels registered on the same Selector.
-
-The disadvantage is the cost of thread context switching.
-
-2. __Same-thread Strategy__
-
-Potentially the most efficient IOStrategy. Unlike the worker-thread IOStrategy, the same-thread IOStrategy processes NIO events in the current thread, avoiding expensive thread context switches.
-
-
-
-
-
-This IOStrategy is still pretty scalable, because we can tune the selector thread pool size, but it does have drawbacks. Care needs to be taken that channel NIO event processing won’t block or execute any long lasting operation, because it may block the processing of other NIO events that occur on the same Selector.
-
-3. __Dynamic Strategy__
-
-As mentioned previously worker-thread and same-thread strategies have distinct advantages and disadvantages. However, what if a strategy could try to swap them smartly during runtime depending on the current conditions (load, gathered statistics… etc)?
-
-
-
-
-
-Potentially this IOStrategy could bring a lot of benefit and allow finer control of the resources. However, it’s important to not overload the condition evaluation logic, as its complexity will make this IOStrategy inefficient comparing to previous two strategies.
-
-By the way, I want you to pay more attention to this strategy, which is probably the best combination of Dubbo server asynchrony.
-
-4. __Leader-follower Strategy__
-
-
-
-
-This IOStrategy is similar to worker-thread IOStrategy, but instead of passing NIO event processing to a worker thread, it changes worker thread to a selector thread by passing it the control over Selector and the actual NIO event processing takes place in the current thread. This strategy actually confuses worker and IO thread stages, which is not recommended.
-
-### Coroutine and thread
-In terms of CPU resource management, the minimum scheduling unit of OS and JVM is thread. The coroutine library implemented by business application through extension can have independent running unit. In fact, it is also done based on thread. The principle should be to save the context and switch to another coroutine when IO blocking or lock waiting is encountered.
-
-__In the default Dubbo thread strategy, there are worker thread pools to execute the business logic, but the ThreadPool Full problem often occurs. In order to release worker threads as soon as possible, another thread will be set up in the implementation of the business service. The cost is thread context switching again, and it's necessary to consider link-level data transfer (such as tracing information) and flow-control export controls, etc. Of course, if Dubbo can switch to the Same- [...]
-
-## The sample
-
-Use an example to experience the Dubbo server-side asynchronous interface. For Demo code, visit [https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-notify](https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-notify)。
-
-```java
-public class AsyncServiceImpl implements AsyncService {
-
- @Override
- public String sayHello(String name) {
- System.out.println("Main sayHello() method start.");
- final AsyncContext asyncContext = RpcContext.startAsync();
- new Thread(() -> {
- asyncContext.signalContextSwitch();
- System.out.println("Attachment from consumer: " + RpcContext.getContext().getAttachment("consumer-key1"));
- System.out.println(" -- Async start.");
- try {
- Thread.sleep(500);
- } catch (InterruptedException e) {
- e.printStackTrace();
- }
- asyncContext.write("Hello " + name + ", response from provider.");
- System.out.println(" -- Async end.");
- }).start();
- System.out.println("Main sayHello() method end.");
- return "hello, " + name;
- }
-
-```
-## Practical suggestions
-* Don't rely too much on server-side asynchrony.
-* Server-side asynchrony is basically a false proposition in the face of event-driven or Reactive.<span data-type="color" style="color:rgb(36, 41, 46)"><span data-type="background" style="background-color:rgb(255, 255, 255)">Supplement the reason: the server asynchrony is said Dubbo server-side business threads (default is 200) is not enough, but in the Event-Driven mode, 200 threads certainly do not need that much, just as much as the number of CPU cores. As long as the business impleme [...]
-* To use server-side asynchrony, it is recommended that the server-side thread strategy adopt the Same_thread pattern + Coroutine Library.
-
-## Conclusions
-When Dubbo supports business applications, it encounters a variety of requirements scenarios, and server-side asynchrony provides users with a solution to deal with ThreadPool Full. In the case of ThreadPool Full, if the current system bottleneck is CPU, this solution is not recommended. If the system load is not high, increasing the number of worker threads or using server asynchrony can be considered.
diff --git a/blog/en-us/first-dubbo-filter.md b/blog/en-us/first-dubbo-filter.md
deleted file mode 100644
index f6eb0ce..0000000
--- a/blog/en-us/first-dubbo-filter.md
+++ /dev/null
@@ -1,212 +0,0 @@
-# First Dubbo Filter
-
-### Overview
-In overall design of Dubbo, Filter is a very important concept, most of Dubbo's functions are based on this
-extension point, and the Filter interception will be executed during each call.
-
-#### Extension Mechanism of Dubbo Filter
-There are already about 20 Filters implemented in Dubbo. Their entry is ProtocolFilterWrapper, ProtocolFilterWrapper
-makes a Wrapper on Protocol and will be loaded when the extension is loaded. Then, let's see how
-the Filter chain is constructed.
-
-```java
-//ProtocolFilterWrapper.java
-public <T> Invoker<T> refer(Class<T> type, URL url) throws RpcException {
- if (Constants.REGISTRY_PROTOCOL.equals(url.getProtocol())) {
- return protocol.refer(type, url);
- }
- return buildInvokerChain(protocol.refer(type, url), Constants.REFERENCE_FILTER_KEY, Constants.CONSUMER);
- }
-
- private static <T> Invoker<T> buildInvokerChain(final Invoker<T> invoker, String key, String group) {
- Invoker<T> last = invoker;
- List<Filter> filters = ExtensionLoader.getExtensionLoader(Filter.class).getActivateExtension(invoker.getUrl(), key, group);
- if (filters.size() > 0) {
- for (int i = filters.size() - 1; i >= 0; i --) {
- final Filter filter = filters.get(i);
- final Invoker<T> next = last;
- last = new Invoker<T>() {
-
- public Class<T> getInterface() {
- return invoker.getInterface();
- }
-
- public URL getUrl() {
- return invoker.getUrl();
- }
-
- public boolean isAvailable() {
- return invoker.isAvailable();
- }
-
- public Result invoke(Invocation invocation) throws RpcException {
- return filter.invoke(next, invocation);
- }
-
- public void destroy() {
- invoker.destroy();
- }
-
- @Override
- public String toString() {
- return invoker.toString();
- }
- };
- }
- }
- return last;
- }
-
-```
-
-#### Activation Mechanism of Dubbo Filter
-Through the above code we can see that, in the method buildInvokerChain, first get all
-activated chains, the chain here is already sorted. Then construct a call chain of Filter
-through the Invoker, finally the constructed call chain can be roughly expressed as: Filter1->Filter2->Filter3->......->Invoker,
-now let's see the detailed flow of the activated chain in the above step.
-
-```java
- public List<T> getActivateExtension(URL url, String key, String group) {
- String value = url.getParameter(key);
- return getActivateExtension(url, value == null || value.length() == 0 ? null : Constants.COMMA_SPLIT_PATTERN.split(value), group);
- }
-
- public List<T> getActivateExtension(URL url, String[] values, String group) {
- List<T> exts = new ArrayList<T>();
-
- List<String> names = values == null ? new ArrayList<String>(0) : Arrays.asList(values);
-
- if (! names.contains(Constants.REMOVE_VALUE_PREFIX + Constants.DEFAULT_KEY)) {
- getExtensionClasses();
- for (Map.Entry<String, Activate> entry : cachedActivates.entrySet()) {
- String name = entry.getKey();
- Activate activate = entry.getValue();
- if (isMatchGroup(group, activate.group())) {
- T ext = getExtension(name);
- if (! names.contains(name) && ! names.contains(Constants.REMOVE_VALUE_PREFIX + name)
- && isActive(activate, url)) {
- exts.add(ext);
- }
- }
- }
- Collections.sort(exts, ActivateComparator.COMPARATOR);
- }
- List<T> usrs = new ArrayList<T>();
- for (int i = 0; i < names.size(); i ++) {
- String name = names.get(i);
- if (! name.startsWith(Constants.REMOVE_VALUE_PREFIX)
- && ! names.contains(Constants.REMOVE_VALUE_PREFIX + name)) {
- if (Constants.DEFAULT_KEY.equals(name)) {
- if (usrs.size() > 0) {
- exts.addAll(0, usrs);
- usrs.clear();
- }
- } else {
- T ext = getExtension(name);
- usrs.add(ext);
- }
- }
- }
- if (usrs.size() > 0) {
- exts.addAll(usrs);
- }
- return exts;
- }
-```
-Through the above code we can see that, some of the Filters configured by the user are activated by default,
-and some need to be activated by the configuration file. The loading order of all Filters is to process Dubbo's
-default Filter first, and then to process the Filter defined by the user. With the "-" configuration, Dubbo's defualt Filter
-can be replaced, with this configuration, the user can flexibly replace or modify the Filter's load order.
-
-#### Built-in Filter of Dubbo
-Dubbo has lots of built-in Filter. RpcContext, accesslog and other functions can be implemented by Dubbo.
-Now let's see the ConsumerContextFilter which used by the Consumer side for context delivery:
-
-```java
-public Result invoke(Invoker<?> invoker, Invocation invocation) throws RpcException {
- RpcContext.getContext()
- .setInvoker(invoker)
- .setInvocation(invocation)
- .setLocalAddress(NetUtils.getLocalHost(), 0)
- .setRemoteAddress(invoker.getUrl().getHost(),
- invoker.getUrl().getPort());
- if (invocation instanceof RpcInvocation) {
- ((RpcInvocation)invocation).setInvoker(invoker);
- }
- try {
- return invoker.invoke(invocation);
- } finally {
- RpcContext.getContext().clearAttachments();
- }
- }
-```
-
-This Filter records the state information during call, and passes the attachments parameter set
-by the client to the server through the invocation object, and these parameters will be cleared
-after the call is completed, which is why the request status information can be recorded by times
-and delivered.
-
-#### Implement A Dubbo Filter
-Because of Dubbo's flexible design and good scalability, we can implement business logic
-in the call chain by implementing our own Dubbo Filter, such as time-consuming statistics, monitor information statistics, etc.
-Now, let's implement a simple Filter:
-
-Maven project structure:
-
-```
-src
- |-main
- |-java
- |-com
- |-xxx
- |-XxxFilter.java (impelement Filter interface)
- |-resources
- |-META-INF
- |-dubbo
- |-com.alibaba.dubbo.rpc.Filter (Plain text file with content：xxx=com.xxx.XxxFilter)
-```
-
-XxxFilter.java：
-
-```java
-public class XxxFilter implements Filter {
- public Result invoke(Invoker<?> invoker, Invocation invocation) throws RpcException {
- // before filter ...
- Result result = invoker.invoke(invocation);
- // after filter ...
- return result;
- }
-}
-```
-
-META-INF/dubbo/com.alibaba.dubbo.rpc.Filter：
-```
-xxx=com.xxx.XxxFilter
-```
-
-configure in xml as:
-
-```xml
-<!-- Consumer call process interception -->
-<dubbo:reference filter="xxx" />
-<!-- Consumer call process default interception，intercept all reference -->
-<dubbo:consumer filter="xxx"/>
-<!-- Provider call process interception -->
-<dubbo:service filter="xxx" />
-<!-- Provider call process default interception，intercept all service -->
-<dubbo:provider filter="xxx"/>
-```
-
-or use annotation as:
-```java
-@Activate(group = "consumer")
-public class XxxFilter implements Filter {
- // ...
-}
-```
-
-Using xml configuration is more flexible and granular.
-
-
-In before and after, you can implement your own business logic to give the filter a certain function.
-Once written and configured, the filter is activated by the Dubbo and executed in the call chain.
diff --git a/blog/en-us/gsoc-2018.md b/blog/en-us/gsoc-2018.md
deleted file mode 100644
index 04d7445..0000000
--- a/blog/en-us/gsoc-2018.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: GSoC 2018
-keywords: Dubbo, GSoC
-description: The GSoC(Google Summer of Code) 2018 projects has been announced
----
-
-The GSoC(Google Summer of Code) 2018 projects has been announced
----
-
-The GSoC(Google Summer of Code) 2018 projects has been announced, Raghu Reddy's project "Extending Serialization protocols support for Apache Dubbo" has been [accepted](https://summerofcode.withgoogle.com/projects/#4747840161579008)! Congratulations!
diff --git a/blog/en-us/introduction-to-dubbo-qos.md b/blog/en-us/introduction-to-dubbo-qos.md
deleted file mode 100644
index eb5c722..0000000
--- a/blog/en-us/introduction-to-dubbo-qos.md
+++ /dev/null
@@ -1,254 +0,0 @@
----
-title: Manipulating Services Dynamically via QoS
-keywords: Dubbo, qos
-description: This article introduces how to use Dubbo's QoS to achieve dynamic configuration.
----
-
-# Manipulating Services Dynamically via QoS
-
-QoS (short form of **Quality of Service**), is a common terminology talking about network devices. For example, by adjusting and manipulating the weights of ports of a router dynamically via QoS, engineers could give priority to services running on these ports and make sure these services' quality and reliability.
-
-In Dubbo, QoS is used to query and manipulate services dynamically, like getting a list of active provider and consumer services, and launching or withdrawing services (i.e registering to or unregistering services from registration center).
-
-## Mechanism of QoS
-
-From 2.5.8, QoS is introduced into Dubbo and is activated by default. All QoS's features are abstracted to commands, which could be executed to get responses from QoS.
-
-> QoS is based on Netty4. In versions earlier than 2.6.x, Dubbo relies on Netty3, so you have to add Netty4 as a dependency explicitly to ensure that Netty4 works. If you generate a Dubbo application on http://start.dubbo.io, there's no need to add configurations because Netty4 is listed as a dependency by default.
-
-
-
-The picture above shows how QoS works:
-
-1. Start and listen to a port (22222 by default).
-2. Choose a corresponding request handler by detecting the protocol (telnet or http) a request comply with.
-3. Decode and parse the request to generate corresponding command according to the protocol.
-4. Execute commands and return with responses.
-
-### QoS Commands:
-
-Commands that QoS supports at the current moment include:
-
-* `help`, list available commands
-* `ls`: list all active provider services and consumer services
-* `online`: dynamically register a service or all services to registration center
-* `offline`: dynamically remove (unregister) a services or all services from registration center
-* `quit`: quit the current telnet session
-
-Now we are going to demonstrate how to manipulate services dynamically via QoS.
-
-#### Access QoS via Telnet
-
-Assuming that our Dubbo server has started, connect to it via telnet:
-
-```shell
-$ telnet localhost 22222
-Trying 127.0.0.1...
-Connected to localhost.
-Escape character is '^]'.
- ????????? ??? ?? ??????????? ??????????? ????????
- ??? ???? ??? ??? ??? ??? ??? ??? ??? ???
- ??? ??? ??? ??? ??? ??? ??? ??? ??? ???
- ??? ??? ??? ??? ?????????? ?????????? ??? ???
- ??? ??? ??? ??? ??????????? ??????????? ??? ???
- ??? ??? ??? ??? ??? ??? ??? ??? ??? ???
- ??? ???? ??? ??? ??? ??? ??? ??? ??? ???
- ????????? ????????? ??????????? ??????????? ????????
-
-
-dubbo>
-```
-
-A `dubbo>` prompt would show up once you connect to server. Now input `help`:
-
-```sh
-dubbo>help
-+---------+----------------------------------------------------------------------------------+
-| help | help command |
-+---------+----------------------------------------------------------------------------------+
-| ls | ls service |
-+---------+----------------------------------------------------------------------------------+
-| offline | offline dubbo |
-+---------+----------------------------------------------------------------------------------+
-| online | online dubbo |
-+---------+----------------------------------------------------------------------------------+
-| quit | quit telnet console |
-+---------+----------------------------------------------------------------------------------+
-
-dubbo>
-```
-
-This command lists all available commands with explanations.
-
-You can also use `help` to a specific command to read examples of that command.
-
-```sh
-dubbo>help online
-+--------------+----------------------------------------------------------------------------------+
-| COMMAND NAME | online |
-+--------------+----------------------------------------------------------------------------------+
-| EXAMPLE | online dubbo |
-| | online xx.xx.xxx.service |
-+--------------+----------------------------------------------------------------------------------+
-```
-
-Use `ls` to check services' status:
-
-```sh
-dubbo>ls
-As Provider side:
-+------------------------------------------+---+
-| Provider Service Name |PUB|
-+------------------------------------------+---+
-|org.apache.dubbo.demo.provider.DemoService| Y |
-+------------------------------------------+---+
-As Consumer side:
-+---------------------+---+
-|Consumer Service Name|NUM|
-+---------------------+---+
-```
-
-There is a service named `org.apache.dubbo.demo.provider.DemoService` in the provider side. `PUB=Y` in the second columns means that the service has been published to the registration center, waiting to be called by the consumer side.
-
-Assuming that we need to withdraw a service dynamically, we can use `offline` command:
-
-```
-dubbo>offline org.apache.dubbo.demo.provider.DemoService
-OK
-```
-
-You can see that the command responds with `OK`. Check the services' status using `ls`:
-
-```sh
-dubbo>ls
-As Provider side:
-+------------------------------------------+---+
-| Provider Service Name |PUB|
-+------------------------------------------+---+
-|org.apache.dubbo.demo.provider.DemoService| N |
-+------------------------------------------+---+
-As Consumer side:
-+---------------------+---+
-|Consumer Service Name|NUM|
-+---------------------+---+
-```
-
-You can see that `PUB` of `org.apache.dubbo.demo.provider.DemoService` has been set to `N`.
-
-Quit the current telnet session using `quit`:
-
-```sh
-dubbo>quit
-BYE!
-Connection closed by foreign host.
-```
-
-#### Access QoS via HTTP
-
-In the example above we performed an offline action to `org.apache.dubbo.demo.provider.DemoService`. Now we are going to demonstrate how to register the service above via HTTP.
-
-```sh
-$ curl -i http://localhost:22222/online?service=org.apache.dubbo.demo.provider.DemoService
-HTTP/1.1 200 OK
-Content-Type: text/plain
-Content-Length: 2
-
-OK%
-```
-
-> Beware of the parameters of online action. They need to be provided in the form of `key=value`. However, `key` would be ignored actually.
-
-The action responds with `OK`. Now use `ls` to check providers' status at the current moment.
-
-```
-$ curl -i http://localhost:22222/ls
-HTTP/1.1 200 OK
-Content-Type: text/plain
-Content-Length: 365
-
-As Provider side:
-+------------------------------------------+---+
-| Provider Service Name |PUB|
-+------------------------------------------+---+
-|org.apache.dubbo.demo.provider.DemoService| Y |
-+------------------------------------------+---+
-As Consumer side:
-+---------------------+---+
-|Consumer Service Name|NUM|
-+---------------------+---+
-```
-
-You can see that the service's `PUB` status has been changed to `Y`.
-
-### QoS' Parameters
-
-You can use parameters that QoS provides to config its startup. These parameters include:
-
-| Parameter | Explanation | Default |
-| ------------------ | ----------------- | ------ |
-| qosEnable | Activate QoS or not | true |
-| qosPort | The port QoS would bind to | 22222 |
-| qosAcceptForeignIp | Enable remote access or not | false |
-
-> Attention. From 2.6.4/2.7.0, `qosAcceptForeignIp` is set to `false` by default, because it's risky if this property is set to `true`. Think twice before you turn it on.
-
-You can configure these parameters in the following ways:
-
-* System property
-* `dubbo.properties`
-* XML
-* Spring-boot auto configuration
-
-They have priority in the following order: system property > `dubbo.properties` > XML > spring-boot.
-
-#### System Property
-
-```
--Ddubbo.application.qos.enable=true
--Ddubbo.application.qos.port=33333
--Ddubbo.application.qos.accept.foreign.ip=false
-```
-
-#### `Dubbo.properties`
-
-Create a `dubbo.properties` file in this directory `src/main/resources` in your project, and copy the following codes into it:
-
-```
-dubbo.application.qos.enable=true
-dubbo.application.qos.port=33333
-dubbo.application.qos.accept.foreign.ip=false
-```
-
-#### XML
-
-If you are going to config using XML, you can try this:
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
- xsi:schemaLocation="http://www.springframework.org/schema/beans
- http://www.springframework.org/schema/beans/spring-beans.xsd
- http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
- <dubbo:application name="demo-provider">
- <dubbo:parameter key="qos.enable" value="true"/>
- <dubbo:parameter key="qos.accept.foreign.ip" value="false"/>
- <dubbo:parameter key="qos.port" value="33333"/>
- </dubbo:application>
- <dubbo:registry address="multicast://224.5.6.7:1234"/>
- <dubbo:protocol name="dubbo" port="20880"/>
- <dubbo:service interface="org.apache.dubbo.demo.provider.DemoService" ref="demoService"/>
- <bean id="demoService" class="org.apache.dubbo.demo.provider.DemoServiceImpl"/>
-</beans>
-```
-
-#### `spring-boot` auto configuration
-
-If you are developing a spring-boot application, you can configure in `application.properties` or `application.yml`:
-
-```
-dubbo.application.qosEnable=true
-dubbo.application.qosPort=33333
-dubbo.application.qosAcceptForeignIp=false
-```
diff --git a/blog/en-us/introduction-to-dubbo-spi-2.md b/blog/en-us/introduction-to-dubbo-spi-2.md
deleted file mode 100644
index 7c9048f..0000000
--- a/blog/en-us/introduction-to-dubbo-spi-2.md
+++ /dev/null
@@ -1,407 +0,0 @@
----
-title: Dubbo extensible mechanism source code analysis
-keywords: Dubbo, SPI, source code analysis
-description: This article introduces the principles and details of Dubbo's SPI.
----
-
-# Dubbo extensible mechanism source code analysis
-
-In the [actual implementation of the Dubbo extensibility mechanism](./introduction-to-dubbo-spi.md), we learned some concepts of the Dubbo extension mechanism, explored the implementation of LoadBalance in Dubbo, and implemented a LoadBalance on our own. Do you think Dubbo's extension mechanism is great? Next, we will go deep into the source code of Dubbo and see what it is.
-
-## ExtensionLoader
-
-`ExtensionLoader` is the core class, which is responsible for the loading and lifecycle management of extension points. Let's start with this class. There are many methods of Extension, and the common methods include:
-
-* `public static <T> ExtensionLoader<T> getExtensionLoader(Class<T> type)`
-* `public T getExtension(String name)`
-* `public T getAdaptiveExtension()`
-
-The common usages are:
-
-* `LoadBalance lb = ExtensionLoader.getExtensionLoader(LoadBalance.class).getExtension(loadbalanceName)`
-* `RouterFactory routerFactory = ExtensionLoader.getExtensionLoader(RouterFactory.class).getAdaptiveExtension()`
-
-Notice: In the source code shown below, I'll remove extraneous code (such as logging, exception catching, and so on) to make it easy to read and understand.
-
-1. getExtensionLoader
- This is a static factory method that enters an extensible interface and returns an ExtensionLoader entity class for this interface. With this entity class, you can get not only a specific extension based on name, but also an adaptive extension.
-
-```java
-public static <T> ExtensionLoader<T> getExtensionLoader(Class<T> type) {
- // An extension point must be an interface
- if (!type.isInterface()) {
- throw new IllegalArgumentException("Extension type(" + type + ") is not interface!");
- }
- // @SPI annotations must be provided
- if (!withExtensionAnnotation(type)) {
- throw new IllegalArgumentException("Extension type without @SPI Annotation!");
- }
- // Get the corresponding ExtensionLoader from the cache according to the interface
- // Each extension will only be loaded once
- ExtensionLoader<T> loader = (ExtensionLoader<T>) EXTENSION_LOADERS.get(type);
- if (loader == null) {
- // Initialize extension
- EXTENSION_LOADERS.putIfAbsent(type, new ExtensionLoader<T>(type));
- loader = (ExtensionLoader<T>) EXTENSION_LOADERS.get(type);
- }
- return loader;
-}
-
-private ExtensionLoader(Class<?> type) {
- this.type = type;
- objectFactory = (type == ExtensionFactory.class ? null : ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension());
-}
-```
-
-2. getExtension
-
-```java
-public T getExtension(String name) {
- Holder<Object> holder = cachedInstances.get(name);
- if (holder == null) {
- cachedInstances.putIfAbsent(name, new Holder<Object>());
- holder = cachedInstances.get(name);
- }
- Object instance = holder.get();
- // Get it from the cache. If it does not exist, create
- if (instance == null) {
- synchronized (holder) {
- instance = holder.get();
- if (instance == null) {
- instance = createExtension(name);
- holder.set(instance);
- }
- }
- }
- return (T) instance;
-}
-```
-Some judgments and caching have been made in the getExtension method, and the main logic is in the createExtension method. Let's move on to the createExtension method.
-
-```java
-private T createExtension(String name) {
- // Get the extension class according to the name of extension point. For example, for LoadBalance, get the RandomLoadBalance class according to random
- Class<?> clazz = getExtensionClasses().get(name);
-
- T instance = (T) EXTENSION_INSTANCES.get(clazz);
- if (instance == null) {
- // Use reflection to call newInstance to create an example of an extension class
- EXTENSION_INSTANCES.putIfAbsent(clazz, (T) clazz.newInstance());
- instance = (T) EXTENSION_INSTANCES.get(clazz);
- }
- // Make dependency injection for the extended class samples
- injectExtension(instance);
- // If there is a wrapper, add the wrapper
- Set<Class<?>> wrapperClasses = cachedWrapperClasses;
- if (wrapperClasses != null && !wrapperClasses.isEmpty()) {
- for (Class<?> wrapperClass : wrapperClasses) {
- instance = injectExtension((T) wrapperClass.getConstructor(type).newInstance(instance));
- }
- }
- return instance;
-}
-```
-The createExtension method has done the following:
-1. First, get the corresponding extension class according to name. Read the extension point configuration file from the `META-INF` folder under ClassPath.
-2. Use reflection to create an instance of an extended class.
-3. make dependency injection for the attributes of the extended class instance. That is, IoC.
-4. If there is a wrapper, add the wrapper. That is, AOP.
-
-Let's focus on these four processes.
-1. Get the corresponding extension class according to name. Let’s read the code first:
-
-```java
-private Map<String, Class<?>> getExtensionClasses() {
- Map<String, Class<?>> classes = cachedClasses.get();
- if (classes == null) {
- synchronized (cachedClasses) {
- classes = cachedClasses.get();
- if (classes == null) {
- classes = loadExtensionClasses();
- cachedClasses.set(classes);
- }
- }
- }
- return classes;
- }
-
-// synchronized in getExtensionClasses
-private Map<String, Class<?>> loadExtensionClasses() {
- final SPI defaultAnnotation = type.getAnnotation(SPI.class);
- if (defaultAnnotation != null) {
- String value = defaultAnnotation.value();
- if (value != null && (value = value.trim()).length() > 0) {
- String[] names = NAME_SEPARATOR.split(value);
- if (names.length > 1) {
- throw new IllegalStateException("more than 1 default extension name on extension " + type.getName());
- }
- if (names.length == 1) cachedDefaultName = names[0];
- }
- }
-
- Map<String, Class<?>> extensionClasses = new HashMap<String, Class<?>>();
- loadFile(extensionClasses, DUBBO_INTERNAL_DIRECTORY);
- loadFile(extensionClasses, DUBBO_DIRECTORY);
- loadFile(extensionClasses, SERVICES_DIRECTORY);
- return extensionClasses;
-}
-```
-This process is very simple. Get the extension class from the cache first, and if it does not exist, load it from the configuration file. The path of the configuration file has been mentioned before:
-* `META-INF/dubbo/internal`
-* `META-INF/dubbo`
-* `META-INF/services`
-
-2. Use reflection to create an extended instance. This process is very simple. We can do this using `clazz.newInstance()`. The attributes of the extended instance created are all null values.
-3. Extended instance is automatic assembly. In the actual scenario, there have dependencies between classes. Dependencies are also referenced in the extended instance, such as a simple Java class, an extension of another Dubbo, or a Spring Bean. The situation of dependencies is complex, and Dubbo's processing is relatively complicated. We will have a special chapter to explain it later. Now, we just need to know that Dubbo can correctly inject common dependencies in extension points, Dub [...]
-4. Extended instance is auto-wrapping. Auto-wrapping is about implementing Spring like AOP functionality. Dubbo uses it to implement some common functions internally, such as logging, monitoring, and so on. The contents of the extended instance auto-wrapper will also be explained separately later.
-
-After the above 4 steps, Dubbo creates and initializes an extended instance. The dependencies of this instance are injected and packaged as needed. At this point, this extended instance can be used.
-
-## Auto-assembly of Dubbo SPI advanced usage
-
-The relevant code for auto-assembly is in the injectExtension method:
-
-```java
-private T injectExtension(T instance) {
- for (Method method : instance.getClass().getMethods()) {
- if (method.getName().startsWith("set")
- && method.getParameterTypes().length == 1
- && Modifier.isPublic(method.getModifiers())) {
- Class<?> pt = method.getParameterTypes()[0];
-
- String property = method.getName().length() > 3 ? method.getName().substring(3, 4).toLowerCase() + method.getName().substring(4) : "";
- Object object = objectFactory.getExtension(pt, property);
- if (object != null) {
- method.invoke(instance, object);
- }
- }
- }
- return instance;
-}
-```
-To accomplish the automatic assembly of dependencies of the extended instances, you first need to know what the dependencies are and what the types of dependencies are. The solution of Dubbo is to find the Java standard setter method. That is, the method name starting with set has only one parameter. If such a set method exists in an extension class, Dubbo injects it into dependencies, which is similar to the injection of Spring's set method. However, dependency injection in Dubbo is mor [...]
-
-```java
-private ExtensionLoader(Class<?> type) {
- this.type = type;
- objectFactory = (type == ExtensionFactory.class ? null : ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension());
-}
-```
-ObjectFacore is also an extension, obtained through `ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension()`.
-
-
-
-
-ExtensionFactory includes three implementations:
-1. SpiExtensionFactory: use Dubbo's Spi to load Extension.
-2. SpringExtensionFactory: load Extension from the Spring container.
-3. AdaptiveExtensionFactory: adaptive AdaptiveExtensionLoader
-
-Pay attention to the AdaptiveExtensionLoader here, the source code is as follows:
-
-```java
-@Adaptive
-public class AdaptiveExtensionFactory implements ExtensionFactory {
-
- private final List<ExtensionFactory> factories;
-
- public AdaptiveExtensionFactory() {
- ExtensionLoader<ExtensionFactory> loader = ExtensionLoader.getExtensionLoader(ExtensionFactory.class);
- List<ExtensionFactory> list = new ArrayList<ExtensionFactory>();
- for (String name : loader.getSupportedExtensions()) {
- list.add(loader.getExtension(name));
- }
- factories = Collections.unmodifiableList(list);
- }
-
- public <T> T getExtension(Class<T> type, String name) {
- for (ExtensionFactory factory : factories) {
- T extension = factory.getExtension(type, name);
- if (extension != null) {
- return extension;
- }
- }
- return null;
- }
-}
-```
-The AdaptiveExtensionLoader class has @Adaptive annotations. As mentioned earlier, Dubbo creates an adaptive instance for each extension. If the extension class has @Adaptive annotations, it will use it as an adaptive class. If not, Dubbo will create one for us. So `ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension())` will return an AdaptiveExtensionLoader instance as an adaptive extension instance.
-The AdaptiveExtensionLoader will iterate through all the ExtensionFactory implementations and try to load the extensions. If found, return. If not, continue to find it in the next ExtensionFactory. Dubbo has two ExtensionFactory built in, which are searched from Dubbo's own extension mechanism and Spring container. Since ExtensionFactory itself is also an extension point, we can implement our own ExtensionFactory to enable automatic assembly of Dubbo to support our custom components. For [...]
-
-## AOP of Dubbo SPI advanced usage
-
-We often use AOP functionality when using Spring. Insert other logic before and after the method of the target class. For example, Spring AOP is usually used to implement logging, monitoring, and authentication, and so on.
-Does Dubbo's extension mechanism also support similar features? The answer is yes. In Dubbo, there is a special class called the Wrapper class. It uses the wrapper class to wrap the original extension point instance through the decorator pattern, and then inserts additional logic before and after the original extension point implementation to implement AOP functionality.
-
-### What is the Wrapper class
-
-So what kind of class is the Wrapper class in the Dubbo extension mechanism? The Wrapper class is a class that has a replication constructor and also is a typical decorator pattern. Here's a Wrapper class:
-
-```java
-class A{
- private A a;
- public A(A a){
- this.a = a;
- }
-}
-```
-Class A has a constructor `public A(A a)`, and the argument to the constructor is A itself. Such a class can be a Wrapper class in the Dubbo extension mechanism. Such Wrapper classes in Dubbo include ProtocolFilterWrapper, ProtocolListenerWrapper, and so on. You can check the source code to deepen your understanding.
-
-### How to configure the Wrapper class
-
-The Wrapper class in Dubbo is also an extension point. Like other extension points, it is also configured in the `META-INF` folder. For example, the ProtocolFilterWrapper and ProtocolListenerWrapper in the previous example are configured in the path `dubbo-rpc/dubbo-rpc-api/src/main/resources/META-INF/dubbo/internal/org.apache.dubbo.rpc.Protocol`:
-```text
-filter=org.apache.dubbo.rpc.protocol.ProtocolFilterWrapper
-listener=org.apache.dubbo.rpc.protocol.ProtocolListenerWrapper
-mock=org.apache.dubbo.rpc.support.MockProtocol
-```
-When Dubbo loads the extension configuration file, there is a piece of code as follows:
-
-```java
-try {
- clazz.getConstructor(type);
- Set<Class<?>> wrappers = cachedWrapperClasses;
- if (wrappers == null) {
- cachedWrapperClasses = new ConcurrentHashSet<Class<?>>();
- wrappers = cachedWrapperClasses;
- }
- wrappers.add(clazz);
-} catch (NoSuchMethodException e) {}
-```
-The meaning of this code is that if the extension class has a copy constructor, it will be saved for later use. The class that has the copy constructor is the Wrapper class. The parameter obtained by `clazz.getConstructor(type)` is the constructor of the extension point interface. Note that the parameter type of the constructor is an extension point interface, not an extension class.
-Take Protocol as an example. The configuration file `dubbo-rpc/dubbo-rpc-api/src/main/resources/META-INF/dubbo/internal/org.apache.dubbo.rpc.Protocol defines filter=org.apache.dubbo.rpc.protocol. ProtocolFilterWrapper`.
-The code of ProtocolFilterWrapper is as follows:
-
-```java
-public class ProtocolFilterWrapper implements Protocol {
-
- private final Protocol protocol;
-
- // One parameter is the copy constructor of Protocol
- public ProtocolFilterWrapper(Protocol protocol) {
- if (protocol == null) {
- throw new IllegalArgumentException("protocol == null");
- }
- this.protocol = protocol;
- }
-}
-```
-ProtocolFilterWrapper has a constructor `public ProtocolFilterWrapper(Protocol protocol)`, and the parameter is the extension point Protocol. So it is a Wrapper class in the Dubbo extension mechanism. The ExtensionLoader will cache it. When creating Extension instances later, the ExtensionLoader use these wrapper classes to wrap the original Extension point in turn.
-
-## Extension point adaptive
-
-As mentioned earlier, Dubbo needs to determine which extension to use based on method parameters at runtime. So there is an extension point adaptive instance. In fact, it is an extension point proxy that delays the selection of extensions from starting Dubbo to calling RPC. Each extension point in Dubbo has an adaptive class. If it is not explicitly provided, Dubbo will automatically create one for us. By default, Javaassist is used.
-Let's first look at the code to create an adaptive extension class:
-
-```java
-public T getAdaptiveExtension() {
- Object instance = cachedAdaptiveInstance.get();
- if (instance == null) {
- synchronized (cachedAdaptiveInstance) {
- instance = cachedAdaptiveInstance.get();
- if (instance == null) {
- instance = createAdaptiveExtension();
- cachedAdaptiveInstance.set(instance);
- }
- }
- }
-
- return (T) instance;
-}
-```
-Continue to read the createAdaptiveExtension method:
-
-```java
-private T createAdaptiveExtension() {
- return injectExtension((T) getAdaptiveExtensionClass().newInstance());
-}
-```
-Continue to read the getAdaptiveExtensionClass method:
-
-```java
-private Class<?> getAdaptiveExtensionClass() {
- getExtensionClasses();
- if (cachedAdaptiveClass != null) {
- return cachedAdaptiveClass;
- }
- return cachedAdaptiveClass = createAdaptiveExtensionClass();
-}
-```
-Continue to read the createAdaptiveExtensionClass method. After a long journey, we finally come to a concrete realization. Look at this createAdaptiveExtensionClass method, which first generates the Java source code for the adaptive class, and then compile the source code into Java bytecode and load it into the JVM.
-
-```java
-private Class<?> createAdaptiveExtensionClass() {
- String code = createAdaptiveExtensionClassCode();
- ClassLoader classLoader = findClassLoader();
- org.apache.dubbo.common.compiler.Compiler compiler = ExtensionLoader.getExtensionLoader(org.apache.dubbo.common.compiler.Compiler.class).getAdaptiveExtension();
- return compiler.compile(code, classLoader);
-}
-```
-The default implementation of Compiler's code is javassist.
-
-```java
-@SPI("javassist")
-public interface Compiler {
- Class<?> compile(String code, ClassLoader classLoader);
-}
-```
-The createAdaptiveExtensionClassCode () method uses a StringBuilder to build Java source code for the adaptive class. The method implementation is relatively long, and the code is not posted here. The approach to bytecode generation is also interesting, first generating Java source code, then compiling it and loading it into the jvm. In this way, the generated Java class can be better controlled. And it doesn't have to care about the API of the bytecode generation framework. Because the [...]
-Below are the Java code example for Protocol adaptive class created by createAdaptiveExtensionClassCode method:
-
-```java
-package org.apache.dubbo.rpc;
-
-import org.apache.dubbo.common.extension.ExtensionLoader;
-
-public class Protocol$Adaptive implements org.apache.dubbo.rpc.Protocol {
- public void destroy() {
- throw new UnsupportedOperationException("method public abstract void org.apache.dubbo.rpc.Protocol.destroy() of interface org.apache.dubbo.rpc.Protocol is not adaptive method!");
- }
-
- public int getDefaultPort() {
- throw new UnsupportedOperationException("method public abstract int org.apache.dubbo.rpc.Protocol.getDefaultPort() of interface org.apache.dubbo.rpc.Protocol is not adaptive method!");
- }
-
- public org.apache.dubbo.rpc.Exporter export(org.apache.dubbo.rpc.Invoker arg0) throws org.apache.dubbo.rpc.RpcException {
- if (arg0 == null) throw new IllegalArgumentException("org.apache.dubbo.rpc.Invoker argument == null");
- if (arg0.getUrl() == null)
- throw new IllegalArgumentException("org.apache.dubbo.rpc.Invoker argument getUrl() == null");
- org.apache.dubbo.common.URL url = arg0.getUrl();
- String extName = (url.getProtocol() == null ? "dubbo" : url.getProtocol());
- if (extName == null)
- throw new IllegalStateException("Fail to get extension(org.apache.dubbo.rpc.Protocol) name from url(" + url.toString() + ") use keys([protocol])");
- org.apache.dubbo.rpc.Protocol extension = (org.apache.dubbo.rpc.Protocol) ExtensionLoader.getExtensionLoader(org.apache.dubbo.rpc.Protocol.class).getExtension(extName);
- return extension.export(arg0);
- }
-
- public org.apache.dubbo.rpc.Invoker refer(java.lang.Class arg0, org.apache.dubbo.common.URL arg1) throws org.apache.dubbo.rpc.RpcException {
- if (arg1 == null) throw new IllegalArgumentException("url == null");
- org.apache.dubbo.common.URL url = arg1;
- String extName = (url.getProtocol() == null ? "dubbo" : url.getProtocol());
- if (extName == null)
- throw new IllegalStateException("Fail to get extension(org.apache.dubbo.rpc.Protocol) name from url(" + url.toString() + ") use keys([protocol])");
- org.apache.dubbo.rpc.Protocol extension = (org.apache.dubbo.rpc.Protocol) ExtensionLoader.getExtensionLoader(org.apache.dubbo.rpc.Protocol.class).getExtension(extName);
- return extension.refer(arg0, arg1);
- }
-}
-```
-The general logic is the same as at the beginning. The parameters are parsed through the url, and the parsed logic is controlled by the value parameter of @adaptive, and then the extension points implementation are obtained according to the name of the extension point. And then finally make the call. If you want to know the specific construction logic of .Java code, you can see the complete implementation of `createAdaptiveExtensionClassCode`.
-In the generated Protocol$Adaptive, both the getDefaultPort and destroy methods are found to throw the exception directly. Why? Take a look at the source code of Protocol:
-
-```java
-@SPI("dubbo")
-public interface Protocol {
-
- int getDefaultPort();
-
- @Adaptive
- <T> Exporter<T> export(Invoker<T> invoker) throws RpcException;
-
- @Adaptive
- <T> Invoker<T> refer(Class<T> type, URL url) throws RpcException;
-
- void destroy();
-}
-```
-As you can see, there are four methods in the Protocol interface, but only the methods of export and refer use the @Adaptive annotation. Dubbo automatically generates adaptive instances, and only the methods modified by @Adaptive has a specific implementation. Therefore, in the Protocol$Adaptive class, only the export and refer methods have specific implementations, and the rest of the methods throw exceptions.
-
diff --git a/blog/en-us/introduction-to-dubbo-spi.md b/blog/en-us/introduction-to-dubbo-spi.md
deleted file mode 100644
index b074ab1..0000000
--- a/blog/en-us/introduction-to-dubbo-spi.md
+++ /dev/null
@@ -1,242 +0,0 @@
----
-title: Dubbo Extension Mechanism in Action
-keywords: Dubbo, SPI
-description: This article introduces Dubbo's SPI mechanism.
----
-
-# Dubbo Extension Mechanism in Action
-
-## 1. Extension Mechanism of Dubbo
-
-Dubbo is claimed as a high-performance RPC framework on its official website. Today, I want to talk about another great specialty of Dubbo --- its scalability. As quote: Rome wasn’t built in a day. Any successful system always starts as a prototype. It is impossible to design a perfect system at the beginning. Instead, we should focus on true demand and keep improving the system. On the coding side, it requires us to pay attention on abstraction layers and high-level isolation. In that [...]
-When talking about software design, people always mention scalability. A framework with good scalability requires the following:
-1.The framework should follow opening/closed principle: software entities should be open for extension, but closed for modification; This means a framework should allow the maintainer to add new functions with as few modifications as possible.
-2.The framework should allow the user to add new functions by adding code on his project without modifying the framework's original source code base.
-With microkernel architecture and extension mechanism, Dubbo satisfies such requirements and achieves good scalability. In the following chapters, we will discuss Dubbo's extension mechanism in detail.
-
-## 2.Extension Solutions
-
-Creating Extensible applications usually considers:
-* Factory method pattern
-* IoC container
-* OSGi (Open Services Gateway initiative)
-
-As a framework, Dubbo does not wish to rely on other IoC containers such as Spring, Guice. OSGi is too complicated to fit Dubbo. In the end, Dubbo SPI is inherited from standard JDK SPI and makes it more powerful.
-
-## 3.Java SPI Mechanism
-
-We will first discuss Java SPI mechanism, which is a basis for understanding Dubbo’s extension mechanism. If you are familiar with Java SPI, you can skip this part.
-
-Java SPI (Service Provider Interface) is a feature for discovering and loading implementations matching a given interface provided in JDK. We can create a text file with the same name as the interface under resource directory `META-INF/services`. The content of the file is the fully qualified class name of the SPI implementation, in which each component is separated by a line breaker. JDK uses `java.util.ServiceLoader` to load implementations of a service. Let us use a simple example to [...]
-
-1. Define an interface IRepository to store data.
-
-```java
-public interface IRepository {
- void save(String data);
-}
-```
-
-2. Create 2 implementations for IRepository: MysqlRepository and MongoRepository
-
-```java
-public class MysqlRepository implements IRepository {
- public void save(String data) {
- System.out.println("Save " + data + " to Mysql");
- }
-}
-```
-
-```java
-public class MongoRepository implements IRepository {
- public void save(String data) {
- System.out.println("Save " + data + " to Mongo");
- }
-}
-```
-
-3. Create a configuration file under `META-INF/services`.
-
-The file name is `META-INF/services/com.demo.IRepository`, the content of file is:
-
-```text
-com.demo.MongoRepository
-com.demo.MysqlRepository
-```
-
-4. Load IRepository using ServiceLoader
-
-```java
-ServiceLoader<IRepository> serviceLoader = ServiceLoader.load(IRepository.class);
-Iterator<IRepository> it = serviceLoader.iterator();
-while (it != null && it.hasNext()){
- IRepository demoService = it.next();
- System.out.println("class:" + demoService.getClass().getName());
- demoService.save("tom");
-}
-```
-In the above example, we created an extension and two of its applications. We created the configuration file in ClassPath and loaded the extensions using ServiceLoader. The final output is:
-class:testDubbo.MongoRepository
-Save tom to Mongo
-class:testDubbo.MysqlRepository
-Save tom to Mysql
-
-## 4. Dubbo SPI Mechanism
-
-Java SPI is simple to use. It also supports basic extension point functions, however, it has some disadvantages:
-* It will load and instantiate all implementations at once to find the requested implementation.
-* The configuration file only includes the extension implementation but does not name them, which makes it hard to reference them in applications.
-* If extensions depend on other extensions, Java SPI cannot automatically load the dependency SPI.
-* It does not provide functions such as IOC or AOP in Spring.
-* It is hard to assemble extensions with other frameworks. For example, if the extension depends on Spring bean, the original Java SPI will not support it.
-
-Therefore, Java SPI is good for some simple scenarios, but does not fit for Dubbo. Dubbo makes some extensions on the original SPI mechanism. We will discuss more about the Dubbo SPI mechanism in the following sections.
-
-## 5. Basic Concepts for Dubbo Extension Point Mechanism
-
-Before diving into Dubbo's extension mechanism，Let us first declare some basic concepts in Dubbo SPI. Those terms will appear multiple times in the following section.
-
-### 5.1 Extension Point
-
-an interface of java.
-
-### 5.2 Extension
-
-an implementation class of the Extension Point
-
-### 5.3 Extension Instance
-
-instance of an extension point implementation class
-
-### 5.4 Extension Adaptive Instance
-
-Maybe it is a little difficult to understand this concept when hearing about it the first time. It may help you understand it better by calling it an extension proxy class. The extension adaptive instance is actually an extension proxy, which implements the method of extension point interface. When calling the interface method of the extension point, it will decide which extension to use according to the actual parameters. For example, the extension point of an IRepository has one save m [...]
-* There are two configurations in Dubbo, one is a fixed system-level configuration and it will not be changed after Dubbo launches. Another is the run-time configuration that may be different for each RPC. For instance, the timeout is configured as 10 seconds in the xml file, which will not change after Dubbo launches. However, for a certain PRC call, we can set its timeout to 30 seconds so as to override the system-level configuration. For Dubbo, the parameters called in each RPC is unk [...]
-* Our class is usually singleton-scaled, such as beans of Spring IoC Container. When instantiating beans, if it depends on some specific extension point, it will know which extension to use, otherwise, the bean will not know how to choose extensions. At this time, a proxy mode is needed, which implements the interface of an extension point. The method can dynamically select the appropriate extension according to the run-time parameters, and this proxy is an adaptive instance. Adaptive e [...]
-
-### 5.5 @SPI
-
-@SPI annotation works on the interface of the extension point, which indicates that the interface is an extension point, and can be loaded by Dubbo ExtentionLoader. If there is no such ExtentionLoader, the call will throw an exception.
-
-### 5.6 @Adaptive
-
-@Adaptive annotation is used on the method that extends the interface, which indicates an adaptive method. When Dubbo generates an adaptive instance for an extension point, if the function has @Adaptive annotation, then Dubbo will generate the corresponding code for the method. The method determines which extension to use according to the parameters. When @Adaptive annotation is used on the class to implement a Decorator class, it is similar to the Decorator pattern, whose major function [...]
-
-### 5.7 ExtentionLoader
-
-Similar to the Java SPI ServiceLoader, it is responsible for loading extensions and life-cycle maintenance.
-
-### 5.8 Extension Alias
-
-Different from Java, each extension in Dubbo has an alias, which is used to reference them in the application, such as
-
-```bash
-random=com.alibaba.dubbo.rpc.cluster.loadbalance.RandomLoadBalance
-roundrobin=com.alibaba.dubbo.rpc.cluster.loadbalance.RoundRobinLoadBalance
-```
-where random, roundrobin are alias of the corresponding extensions, and we can directly use them in the configuration file.
-
-### 5.9 Paths
-
-Similar to the way Java SPI loading the extension configuration from the `META-INF/services` directory, Dubbo will also load the extension configuration file from the following path:
-* `META-INF/dubbo/internal`
-* `META-INF/dubbo`
-* `META-INF/services`
-
-## 6. Interpretation for Dubbo's LoadBalance Extension Point
-
-Now that we know some basic idea about Dubbo, let us check a practical extension point in Dubbo to get some intuition.
-
-We take the Dubbo’s LoadBalance extension point as an example. A service in Dubbo usually has multiple providers. When a consumer calls the service, he needs to choose one of the providers. This is an example of LoadBalance. Now, let us figure out how LoadBalance becomes an extension point in Dubbo.
-
-
-### 6.1 LoadBalance Interfance
-
-```java
-@SPI(RandomLoadBalance.NAME)
-public interface LoadBalance {
-
- @Adaptive("loadbalance")
- <T> Invoker<T> select(List<Invoker<T>> invokers, URL url, Invocation invocation) throws RpcException;
-}
-```
-LoadBalance interface has only one select method. Select method chose one invoker among multiple invokers. In the code above, the elements related to Dubbo SPI are:
-* @SPI([RandomLoadBalance.NAME](http://RandomLoadBalance.NAME)) @SPI is used for LoadBalance interface, which indicates that the LoadBalance interface is an extension point. Without the @SPI annotation, if we try to load the extension, it will throw an exception. @SPI annotation has one parameter, and this parameter represents the Alias of the default implementation of the extension point. If there has no explicitly specified extension, the default implementation will be used.
-`RandomLoadBalance.NAME` is a constant with value “random” and is a random load balancing implementation. The definition of random is in the configuration file `META-INF/dubbo/internal/com.alibaba.dubbo.rpc.cluster.LoadBalance`:
-
-```bash
-random=com.alibaba.dubbo.rpc.cluster.loadbalance.RandomLoadBalance
-roundrobin=com.alibaba.dubbo.rpc.cluster.loadbalance.RoundRobinLoadBalance
-leastactive=com.alibaba.dubbo.rpc.cluster.loadbalance.LeastActiveLoadBalance
-consistenthash=com.alibaba.dubbo.rpc.cluster.loadbalance.ConsistentHashLoadBalance
-```
-There are four extension implementations of LoadBalance defined in the configuration file. The implementation of load balancing will not be covered in this article. The only thing we need to know is that Dubbo provides four kinds of load balancing implementations. We can explicitly specify an implementation by using xml file, properties file or JVM parameter. If there has no explicitly specified implementation, Dubbo will use random as default.
-
-
-
-
-* @Adaptive("loadbalance") Applying @Adaptive annotation on select method indicates that select method is an adaptive method. Dubbo will automatically generate the corresponding code for the method. When select method is called, it will decide which extension to apply based on the method parameters. @Adaptive parameter `loadbalance` indicates that the value of loadbalance in method is the extension implementation that will be actually called. However, we cannot find loadbalance paramete [...]
-
-### 6.2 Obtain LoadBalance extension
-
-The code of LoadBalance in Dubbo is as follows:
-
-```java
-LoadBalance lb = ExtensionLoader.getExtensionLoader(LoadBalance.class).getExtension(loadbalanceName);
-```
-Using ExtensionLoader.getExtensionLoader(LoadBalance.class) method to obtain an implementation of ExtensionLoader, then we call getExtension and pass an extension alias to obtain the corresponding extension implementation.
-
-## 7. Customize a LoadBalance Extension
-
-In this session, we will use a simple example to implement a LoadBalance and integrate it into Dubbo. I will show some important steps and codes, and the complete demo can be downloaded from the following address([https://github.com/vangoleo/dubbo-spi-demo](https://github.com/vangoleo/dubbo-spi-demo)).
-
-### 7.1 implement LoadBalance Interface
-
-First, we build a LoadBalance instance. Since we just need the instance to demonstrate Dubbo extension mechanism, it will be very simple. We choose the first invoker and print a log sentence in the console.
-
-```java
-package com.dubbo.spi.demo.consumer;
-public class DemoLoadBalance implements LoadBalance {
- @Override
- public <T> Invoker<T> select(List<Invoker<T>> invokers, URL url, Invocation invocation) throws RpcException {
- System.out.println("DemoLoadBalance: Select the first invoker...");
- return invokers.get(0);
- }
-}
-```
-
-### 7.2 Add extension configuration file
-
-Add file:`META-INF/dubbo/com.alibaba.dubbo.rpc.cluster.LoadBalance`. The content of file is:
-
-```bash
-demo=com.dubbo.spi.demo.consumer.DemoLoadBalance
-```
-
-### 7.3 Configure customized LoadBalance
-
-Through the above 2 steps, we have already added a LoadBalance implementation named demo, and set up the configuration file. In the next step, we need to explicitly tell Dubbo to implement the demo while doing load balancing. If we use Dubbo through spring, we could set it up in the xml file.
-
-```xml
-<dubbo:reference id="helloService" interface="com.dubbo.spi.demo.api.IHelloService" loadbalance="demo" />
-```
-Configure <loadbalance="demo"> in [dubbo:reference](dubbo:reference) at consumer part.
-
-### 7.4 launch Dubbo
-
-Launch Dubbo and call IHelloService, the console will output log: `DemoLoadBalance: Select the first invoker...`, which means Dubbo does use our customized LoadBalance.
-
-
-## Summary
-
-So far, we learnt the basic concepts of Dubbo SPI beginning with Java SPI, and we used LoadBalance in Dubbo as an example to help us understand better. Finally, we practiced and created a customized LoadBalance and integrated it to Dubbo. We believe that combining concepts and practice, everyone can get a better idea of Dubbo’s scalability. To summarize, Dubbo SPI has the following features:
-* Build extensions on Dubbo does not require modifications on the original source code base.
-* The customized Dubbo extension point implementation is a normal Java class. Dubbo does not introduce any specialized elements, and have almost zero code intrusion.
-*Extension registration on Dubbo requires only configuration file under the ClassPath directory. It is simple to use and has no effect on the existing code. This meets opening/closed principle.
-* Dubbo's extension mechanism default: @SPI("dubbo") represents the default SPI object.
-* Dubbo's extension mechanism supports the advanced features such as IoC and AoP, etc.
-* Dubbo's extension mechanism supports third-party IoC containers. It supports Spring beans by default and can be extended to other containers, such as Google/Guice.
-* It is easy to switch the implementation of the extension point because it requires only modifications on the specific implementation in the configuration file without changing the code.
-
-
-In the next article, we will go deep and check Dubbo's source code to learn more about Dubbo's extensibility mechanism.
diff --git a/blog/en-us/pinpoint.md b/blog/en-us/pinpoint.md
deleted file mode 100644
index a537f32..0000000
--- a/blog/en-us/pinpoint.md
+++ /dev/null
@@ -1,417 +0,0 @@
----
-title: Tracking with Pinpoint
-keywords: Dubbo, Pinpoint, tracing
-description: This article introduces how to use Pinpoint to track Dubbo applications and monitor applications' performance.
----
-
-# Tracking with Pinpoint
-
-After using Dubbo to serve or integrate applications, assuming that a service backstage log shows an exception and that the service is invoked by multiple applications, it is often difficult to determine which application is called, and what is the cause of the problem, so we need a set of distributed tracking systems to quickly locate the problem. Pinpoint can help us quickly locate problems (of course, there are more than one solution).
-
-## What is Pinpoint
-
-[Pinpoint](https://github.com/naver/pinpoint) is an APM (Application Performance Management) tool for large-scale distributed systems written in Java. Inspired by Dapper, Pinpoint provides a solution to help analyze the overall structure of the system and how components within them are interconnected by tracing transactions across distributed applications.
-
-You should definitely check Pinpoint out If you want to
-
-understand your application topology at a glance
-monitor your application in Real-Time
-gain code-level visibility to every transaction
-install APM Agents without changing a single line of code
-have minimal impact on the performance (approximately 3% increase in resource usage)
-
-### ServerMap
-
-Understand the topology of any distributed systems by visualizing how their components are interconnected. Clicking on a node reveals details about the component, such as its current status, and transaction count.
-
-### Realtime Active Thread Chart
-
-Monitor active threads inside applications in real-time.
-
-### Request/Response Scatter Chart
-
-Visualize request count and response patterns over time to identify potential problems. Transactions can be selected for additional detail by dragging over the chart.
-
-### CallStack
-
-Gain code-level visibility to every transaction in a distributed environment, identifying bottlenecks and points of failure in a single view.
-
-### Inspector
-
-View additional details on the application such as CPU usage, Memory/Garbage Collection, TPS, and JVM arguments.
-
-### Supported Modules (last updated 2018/04/01)
-
-* JDK 6+
-* Tomcat 6/7/8, Jetty 8/9, JBoss EAP 6, Resin 4, Websphere 6/7/8, Vertx 3.3/3.4/3.5
-* Spring, Spring Boot (Embedded Tomcat, Jetty)
-* Apache HTTP Client 3.x/4.x, JDK HttpConnector, GoogleHttpClient, OkHttpClient, NingAsyncHttpClient
-* Thrift Client, Thrift Service, DUBBO PROVIDER, DUBBO CONSUMER
-* ActiveMQ, RabbitMQ
-* MySQL, Oracle, MSSQL, CUBRID,POSTGRESQL, MARIA
-* Arcus, Memcached, Redis, CASSANDRA
-* iBATIS, MyBatis
-* DBCP, DBCP2, HIKARICP
-* gson, Jackson, Json Lib
-* log4j, Logback
-
-## Pinpoint and Dubbo
-
-### Quickstart Pinpoint
-
-[Quick start](http://naver.github.io/pinpoint/quickstart.html)（No neet to start TestApp）
-
-### Dubbo demo
-
-#### Create API module
-
-pom.xml
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<project xmlns="http://maven.apache.org/POM/4.0.0"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
- <modelVersion>4.0.0</modelVersion>
-
- <groupId>com.example</groupId>
- <artifactId>demo-api</artifactId>
- <version>0.0.1-SNAPSHOT</version>
-</project>
-```
-
-Create API interface：
-```
-package com.example.demoapi;
-
-public interface HelloService {
- String sayHello(String name);
-}
-```
-
-#### Dubbo provider
-
-pom.xml
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
- <modelVersion>4.0.0</modelVersion>
-
- <groupId>com.example</groupId>
- <artifactId>demo-provider</artifactId>
- <version>0.0.1-SNAPSHOT</version>
- <packaging>jar</packaging>
-
- <name>demo-provider</name>
-
- <parent>
- <groupId>org.springframework.boot</groupId>
- <artifactId>spring-boot-starter-parent</artifactId>
- <version>2.0.3.RELEASE</version>
- <relativePath/> <!-- lookup parent from repository -->
- </parent>
-
- <properties>
- <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
- <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
- <java.version>1.8</java.version>
- </properties>
-
- <repositories>
- <repository>
- <id>sonatype-nexus-snapshots</id>
- <url>https://oss.sonatype.org/content/repositories/snapshots</url>
- <releases>
- <enabled>false</enabled>
- </releases>
- <snapshots>
- <enabled>true</enabled>
- </snapshots>
- </repository>
- </repositories>
-
- <dependencies>
- <dependency>
- <groupId>org.springframework.boot</groupId>
- <artifactId>spring-boot-starter</artifactId>
- </dependency>
- <dependency>
- <groupId>com.alibaba.boot</groupId>
- <artifactId>dubbo-spring-boot-starter</artifactId>
- <version>0.2.0</version>
- </dependency>
- <dependency>
- <groupId>com.example</groupId>
- <artifactId>demo-api</artifactId>
- <version>0.0.1-SNAPSHOT</version>
- </dependency>
-
- <dependency>
- <groupId>org.springframework.boot</groupId>
- <artifactId>spring-boot-starter-test</artifactId>
- <scope>test</scope>
- </dependency>
- </dependencies>
-
- <build>
- <plugins>
- <plugin>
- <groupId>org.springframework.boot</groupId>
- <artifactId>spring-boot-maven-plugin</artifactId>
- </plugin>
- </plugins>
- </build>
-
-</project>
-```
-
-1. `HelloService` interface：
-```java
-package com.example.demoprovider.provider;
-
-import com.alibaba.dubbo.config.annotation.Service;
-import com.example.demoapi.HelloService;
-
-@Service(version = "${demo.service.version}",
- application = "${dubbo.application.id}",
- protocol = "${dubbo.protocol.id}",
- registry = "${dubbo.registry.id}")
-public class HelloServiceImpl implements HelloService {
- static int i = 0;
- @Override
- public String sayHello(String name) {
- i++;
- if (i % 3 == 0) {
- throw new RuntimeException("ex");
- }
- return "Hello " + name + "!";
- }
-}
-```
-
-2. Spring Boot bootstrap：
-```java
-package com.example.demoprovider;
-
-import org.springframework.boot.SpringApplication;
-import org.springframework.boot.autoconfigure.SpringBootApplication;
-
-@SpringBootApplication
-public class DemoProviderApplication {
-
- public static void main(String[] args) {
- SpringApplication.run(DemoProviderApplication.class, args);
- }
-}
-```
-
-3. `application.properties`：
-
-```properties
-# Spring boot application
-spring.application.name = dubbo-provider-demo
-server.port = 9090
-management.port = 9091
-
-# Service version
-demo.service.version = 1.0.0
-
-# Base packages to scan Dubbo Components (e.g @Service , @Reference)
-dubbo.scan.basePackages = com.example.demoprovider
-
-# Dubbo Config properties
-## ApplicationConfig Bean
-dubbo.application.id = dubbo-provider-demo
-dubbo.application.name = dubbo-provider-demo
-
-## ProtocolConfig Bean
-dubbo.protocol.id = dubbo
-dubbo.protocol.name = dubbo
-dubbo.protocol.port = 12345
-
-## RegistryConfig Bean
-dubbo.registry.id = my-registry
-dubbo.registry.address = N/A
-```
-
-#### Dubbo consumer
-
-pom.xml
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
- <modelVersion>4.0.0</modelVersion>
-
- <groupId>com.example</groupId>
- <artifactId>demo-consumer</artifactId>
- <version>0.0.1-SNAPSHOT</version>
- <packaging>jar</packaging>
-
- <name>demo-consumer</name>
-
- <parent>
- <groupId>org.springframework.boot</groupId>
- <artifactId>spring-boot-starter-parent</artifactId>
- <version>2.0.3.RELEASE</version>
- <relativePath/> <!-- lookup parent from repository -->
- </parent>
-
- <properties>
- <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
- <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
- <java.version>1.8</java.version>
- </properties>
-
- <repositories>
- <repository>
- <id>sonatype-nexus-snapshots</id>
- <url>https://oss.sonatype.org/content/repositories/snapshots</url>
- <releases>
- <enabled>false</enabled>
- </releases>
- <snapshots>
- <enabled>true</enabled>
- </snapshots>
- </repository>
- </repositories>
-
- <dependencies>
- <dependency>
- <groupId>org.springframework.boot</groupId>
- <artifactId>spring-boot-starter-web</artifactId>
- </dependency>
- <dependency>
- <groupId>com.alibaba.boot</groupId>
- <artifactId>dubbo-spring-boot-starter</artifactId>
- <version>0.2.0</version>
- </dependency>
- <dependency>
- <groupId>com.example</groupId>
- <artifactId>demo-api</artifactId>
- <version>0.0.1-SNAPSHOT</version>
- </dependency>
-
- <dependency>
- <groupId>org.springframework.boot</groupId>
- <artifactId>spring-boot-starter-test</artifactId>
- <scope>test</scope>
- </dependency>
- </dependencies>
-
- <build>
- <plugins>
- <plugin>
- <groupId>org.springframework.boot</groupId>
- <artifactId>spring-boot-maven-plugin</artifactId>
- <configuration>
- <classifier>exec</classifier>
- </configuration>
- </plugin>
- </plugins>
- </build>
-
-</project>
-```
-
-1. `@Reference` injection `HelloService`
-```java
-package com.example.democonsumer.controller;
-
-import com.alibaba.dubbo.config.annotation.Reference;
-import com.example.demoapi.HelloService;
-import org.springframework.web.bind.annotation.RequestMapping;
-import org.springframework.web.bind.annotation.RequestParam;
-import org.springframework.web.bind.annotation.RestController;
-
-@RestController
-public class DemoConsumerController {
- @Reference(version = "${demo.service.version}",
- application = "${dubbo.application.id}",
- url = "dubbo://<Real IP Address>:12345")
- private HelloService helloService;
-
- @RequestMapping("/sayHello")
- public String sayHello(@RequestParam String name) {
- return helloService.sayHello(name);
- }
-}
-```
-
-2. Spring Boot bootstrap:
-```java
-package com.example.democonsumer;
-
-import org.springframework.boot.SpringApplication;
-import org.springframework.boot.autoconfigure.SpringBootApplication;
-
-@SpringBootApplication
-public class DemoConsumerApplication {
-
- public static void main(String[] args) {
- SpringApplication.run(DemoConsumerApplication.class, args);
- }
-}
-```
-
-3. `application.properties`:
-```properties
-# Spring boot application
-spring.application.name=dubbo-consumer-demo
-server.port=8080
-management.port=8081
-
-# Service Version
-demo.service.version=1.0.0
-
-# Dubbo Config properties
-## ApplicationConfig Bean
-dubbo.application.id=dubbo-consumer-demo
-dubbo.application.name=dubbo-consumer-demo
-
-## ProtocolConfig Bean
-dubbo.protocol.id=dubbo
-dubbo.protocol.name=dubbo
-dubbo.protocol.port=12345
-```
-
-### Using Pinpoint-agent to start `Dubbo provider` and `Dubbo consumer`
-
-1. Maven clean package
-```
-mvn clean package
-```
-
-2. Start provider
-```
-java -jar -javaagent:$AGENT_PATH/pinpoint-bootstrap-$VERSION.jar -Dpinpoint.agentId=demo-provider -Dpinpoint.applicationName=DP target/demo-provider-0.0.1-SNAPSHOT.jar
-```
-
-3. Start consumer
-```
-java -jar -javaagent:$AGENT_PATH/pinpoint-bootstrap-$VERSION.jar -Dpinpoint.agentId=demo-consumer -Dpinpoint.applicationName=DC target/demo-comsumer-0.0.1-SNAPSHOT-exec.jar
-```
-
-4. Access the consumer address to simulate user requests
-
-`http://localhost:8080/sayHello?name=ABC`
-
-## Using Pinpoint locate problems
-
-### Homepage
-
-
-
-> The user request here is double the number of requests for DubboProvider, because the favicon.ico icon request is recorded.
-
-### Call tree
-
-
-
-### Mixed view
-
-
-
-### Other
-
-The example simply simulates the provision and call of Dubbo, and does not carry out the application of other middleware such as database. For detailed use, please refer to the Pinpoint document.
diff --git a/blog/en-us/prepare-an-apache-release.md b/blog/en-us/prepare-an-apache-release.md
deleted file mode 100644
index a0cd640..0000000
--- a/blog/en-us/prepare-an-apache-release.md
+++ /dev/null
@@ -1,518 +0,0 @@
----
-title: Understanding the Apache Release Cycle
-keywords: Dubbo, Apache, Release
-description: This article introduces how to the Apache publish content and process
----
-# How to prepare an the Apache Release
-
-## Understanding the Apache Release Cycle
-
-In general, Source Release is the key and the required content of Apache. But Binary Release is optional, Dubbo can choose whether to release binary packages to the Apache repository or to the Maven central repository.
-
-Please refer to the following links for more information on ASF's release guide:
-
-- [Apache Release Guide](http://www.apache.org/dev/release-publishing)
-- [Apache Release Policy](http://www.apache.org/dev/release.html)
-- [Maven Release Info](http://www.apache.org/dev/publishing-maven-artifacts.html)
-
-## Preparation of Local Building Environment
-
-Mainly including the related preparation of signature utilities and Maven repository certification
-
-1. Install GPG,refer to https://www.gnupg.org/download/index.html
-
- - For example, in Mac OS
-
- ```sh
- $ brew install gpg
- $ gpg --version #check version,should be 2.x
- ```
-
-2. Generate the key with GPG
-
- - Generate the key according to the prompt
-
- ```shell
- $ gpg2 --full-gen-key
- gpg (GnuPG) 2.0.12; Copyright (C) 2009 Free Software Foundation, Inc.
- This is free software: you are free to change and redistribute it.
- There is NO WARRANTY, to the extent permitted by law.
-
- Please select what kind of key you want:
- (1) RSA and RSA (default)
- (2) DSA and Elgamal
- (3) DSA (sign only)
- (4) RSA (sign only)
- Your selection? 1
- RSA keys may be between 1024 and 4096 bits long.
- What keysize do you want? (2048) 4096
- Requested keysize is 4096 bits
- Please specify how long the key should be valid.
- 0 = key does not expire
- <n> = key expires in n days
- <n>w = key expires in n weeks
- <n>m = key expires in n months
- <n>y = key expires in n years
- Key is valid for? (0)
- Key does not expire at all
- Is this correct? (y/N) y
-
- GnuPG needs to construct a user ID to identify your key.
-
- Real name: Robert Burrell Donkin
- Email address: rdonkin@apache.org
- Comment: CODE SIGNING KEY
- You selected this USER-ID:
- "Robert Burrell Donkin (CODE SIGNING KEY) <rd...@apache.org>"
-
- Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
- You need a Passphrase to protect your secret key. # enter the password, which will be used frequently when packaging.
- ```
-
- - View key id
-
- ```sh
- $ gpg --list-keys
- pub rsa4096/28681CB1 2018-04-26 # 28681CB1 is the key id
- uid [ultimate] liujun (apache-dubbo) <li...@apache.org>
- sub rsa4096/D3D6984B 2018-04-26
-
- ########### Note: Different diaplay for different version.
- $ gpg --list-keys
- pub rsa4096 2018-11-12 [SC]
- 63AAE9838F4A303E40BAF5FEA3A1CA7A5D4A3981 # Last 8 character(5D4A3981) as key id，it will be used when send public key to keyserver
- uid [ 绝对 ] Victory Cao (CODE SIGNING KEY) <vi...@apache.org>
- sub rsa4096 2018-11-12 [E]
-
-
- # send public key to keyserver via key id
- $ gpg --keyserver pgpkeys.mit.edu --send-key 28681CB1
- # Here pgpkeys.mit.edu is a random selection of keyserver. Any key server from the list https://sks-keyservers.net/status/ is acceptable because they are automatically synchronized.
- ```
-
- - If there are multiple public keys，you can set the default key
-
- ~/.gnupg/gpg.conf
-
- ```proper
- # If you have more than 1 secret key in your keyring, you may want to
- # uncomment the following option and set your preferred keyid.
-
- default-key 28681CB1
- ```
-
- - If there are multiple public keys, you can also delete unuseful key：
-
- ```sh
- ### Delete the private key first, then delete the public key.
-
- $ gpg --yes --delete-secret-keys shenglicao2@gmail.com ### indicate email address
-
- $ gpg --delete-keys 1808C6444C781C0AEA0AAD4C4D6A8007D20DB8A4
-
- ```
-
-3. Set up Apache central repository.
-
- - The parent pom of Dubbo project is apache pom
-
- ```xml
- <parent>
- <groupId>org.apache</groupId>
- <artifactId>apache</artifactId>
- <version>19</version>
- </parent>
- ```
-
- - Add the following contents to .m2/settings.xml
-
- Enter the passwords after
- encrypting by [maven-encryption-plugin](http://maven.apache.org/guides/mini/guide-encryption.html)
-
- ```xml
- <settings>
- ...
- <servers>
- <!-- To publish a snapshot of some part of Maven -->
- <server>
- <id>apache.snapshots.https</id>
- <username> <!-- YOUR APACHE LDAP USERNAME --> </username>
- <password> <!-- YOUR APACHE LDAP PASSWORD (encrypted) --> </password>
- </server>
- <!-- To stage a release of some part of Maven -->
- <server>
- <id>apache.releases.https</id>
- <username> <!-- YOUR APACHE LDAP USERNAME --> </username>
- <password> <!-- YOUR APACHE LDAP PASSWORD (encrypted) --> </password>
- </server>
- ...
- <!-- gpg passphrase used when generate key -->
- <server>
- <id>gpg.passphrase</id>
- <passphrase><!-- yourKeyPassword --></passphrase>
- </server>
- </servers>
- </settings>
- ```
-
-
-## Pack & Upload
-
-1. Pull the new branch from the master branch as the release branch. If you want to release the ${release_version} version now, pull the new branch ${release_version}-release from 2.6.x. Then the
-modifications and taggings related to ${release_version} Release Candidates are applied to ${release_version}-release branch, and is merged into the master branch after the final release.
-
-2. First of all, verify that the maven component packing, source packing, signature, etc are working properly on the ${release_version}-release branch.
-
- ```shell
- $ mvn clean install -Papache-release
- $ mvn deploy
- ```
-
- This push the snapshot package to the maven central repository.
-
-3. Release with maven-release-plugin
-
- - verify with dryRun
-
- ```shell
- $ mvn release:prepare -Prelease -Darguments="-Dmaven.test.skip=true" -DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID -DdryRun=true
- ```
-
- - After verification, run release:prepare
-
- ```shell
- $ mvn release:clean
- $ mvn release:prepare -Prelease -Darguments="-Dmaven.test.skip=true" -DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID -DpushChanges=false
- ```
-
- > If you are promted to input password for pushing to GitHub (basically including adding new commits and tags), do not input your login password of GitHub. Use `Personal access tokens` instead. You can go to https://github.com/settings/profile, click `Developer settings` -> `Personal access tokens`, and generate a new token if not. Please refer to this [guide](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) for more infomation.
- > you need to choose the release artifactId, next artifactId and the release tag, the default tag is dubbo-parent-xxxx, you need to change it to dubbo-xxxx
-
-
- After executing the above commands, you will find that:
- 1. source-release.zip and bin-release.zip are generated under dubbo-distribution directory, please unzip it and check the file structure
- 2. `-DpushChanges=false` tells maven not to push the commits and tags to the remote repostiroy. If not specified, the version tag will be pushed to github repository, you will see a commit called `[maven-release-plugin] prepare release dubbo-x.x.x` added.
- 3. The branch version is upgraded to ${release_version+1}-SNAPSHOT automatically. If `-DpushChanges=true` is specified, the modifications will be pushed to the remote repository, you will see a commit called `[maven-release-plugin] prepare for next development iteration` added.
-
- If `-DpushChanges=false` is specified, you will have to manually push the commit to remote repository before go to next step.
-
- - Run release:perform
-
- ```shell
- $ mvn release:perform -Prelease -Darguments="-Dmaven.test.skip=true" -DautoVersionSubmodules=true -Dusername=YOUR GITHUB ID
- ```
-
- Maven will download the source code from the tag you just pushed, compile it, and deploy to remote maven repsoitry in staging state.
-
-### Note
-
-> When you deploy the package into repository, it will be interrupted for network. So you must restart to desploy.
-> The problem is that missing package occurred many times at deploying. So you should check the quantity of package, especially parent package.
-
-## Prepare Apache Release
-
-1. Prepare the svn local environment (Apache hosting the release content of project by svn)
-
-2. Checkout dubbo to local directory
-
- ```shell
- $ svn checkout https://dist.apache.org/repos/dist/dev/incubator/dubbo
- ```
- Assume that the local directory is `~/apache/incubator/dubbo`
-
-3. The current release version is ${release_version}, new directory
-
- ```shell
- $ cd ~/apache/incubator/dubbo # dubbo svn root directory
- $ mkdir ${release_version}
- ```
-
-4. Add public key to [KEYS](https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS) file if you are the first time to be a release manager. KEYS is mainly used to allow people who participate in the voting to be imported locally to verify the correctness of the sign.
-
- ```shell
- $ gpg -a --export your_key_id >> KEYS
- ```
-
- For more information on how to get your key id, please refer to this [guide](https://help.github.com/articles/generating-a-new-gpg-key/)
-
-5. Copy the source.zip package from the Dubbo root directory to the svn local repository dubbo/${release_version}
-
-6. Generate sha512 sign
-
- For source-release.zip
-
- ```shell
- $ shasum -a 512 apache-dubbo-${release_version}-source-release.zip >> apache-dubbo-${release_version}-source-release.zip.sha512
- ```
-
- For bin-release.zip
-
- Please add `-b` paramter when generating sha512 for bin-release.zip, which indicates it is a binary file.
-
- ```shell
- $ shasum -b -a 512 apache-dubbo-${release_version}-bin-release.zip >> apache-dubbo-${release_version}-bin-release.zip.sha512
- ```
- You should generate something like this:
-
- ```
- b8f13d1df6d6c9a1facc72fafc00b2d22bea1e600517c507467d8fca2f776a7a3877101742da53114bfa629ca5b941eb4d9ef989de43f0833e2a794e7ccf5c8a *apache-dubbo-spring-boot-project-2.7.0-bin-release.zip
- ```
-
- Note there is a `*` sign before the file name.
-
-7. If the binary release is accompanied with the source release. Run the following command in the dubbo-distribution module:
-
- ```shell
- $ mvn install
- ```
- Go to target directory, copy bin-release.zip and bin-release.zip.asc to svn local repository dubbo/${release_version}, and refer to step 6 to generate sha512 sign.
-
-8. Commit to Apache svn
-
- ```shell
- $ svn status
- $ svn commit -m 'prepare for ${release_version} RC1'
- ```
-
-## Verify Release Candidates
-
-**A full check list can be found [here](https://wiki.apache.org/incubator/IncubatorReleaseChecklist)**
-
-The verification link includes but is not limited to the following contents and forms:
-
-### Check signatures and hashes are good
-
-#### check the sha512 sum
-
-
-```sh
-$ shasum -c apache-dubbo-${release_version}-source-release.zip.sha512
-$ shasum -c apache-dubbo-${release_version}-bin-release.zip.sha512
-```
-#### check the gpg signarure
-
-If it's your first time verify a release candidte, you should import public keys first.
-
-```sh
... 922895 lines suppressed ...