This is an automated email from the ASF dual-hosted git repository.
min pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-dubbo-ops.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new a42caaa Created The compatibility of Dubbo Admin (markdown)
a42caaa is described below
commit a42caaaf1ff364469ba4c22c2ebd99775ada158b
Author: min <[email protected]>
AuthorDate: Fri Jan 11 16:11:37 2019 +0800
Created The compatibility of Dubbo Admin (markdown)
---
The-compatibility-of-Dubbo-Admin.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/The-compatibility-of-Dubbo-Admin.md
b/The-compatibility-of-Dubbo-Admin.md
new file mode 100644
index 0000000..e611280
--- /dev/null
+++ b/The-compatibility-of-Dubbo-Admin.md
@@ -0,0 +1,7 @@
+* The mainstream version of Dubbo are Dubbo 2.6 and Dubbo 2.7
+* The most different of these two version are configuration center: Dubbo 2.6
puts all data on register center, Dubbo 2.7 divided it into registry center,
configuration center and metadata center.
+* Dubbo Admin's manipulation of configuration is the same as Dubbo 2.7, please
refer to [Dubbo Admin configuration
+](https://github.com/apache/incubator-dubbo-ops/wiki/Dubbo-Admin-configuration).
It also compatible with Dubbo 2.7, here 'compatible' means:
+ * Service scope configuration will register to both Dubbo 2.7 and Dubbo
2.6，thus, the client of Dubbo 2.6 can receive and parse it.
+ * Application scope configuration(including tag router) will register to
Dubbo 2.7 only, because this is the new feature in Dubbo 2.7
+ * Dubbo Admin will read configurations in the protocol of Dubbo 2.7 only, so
the legacy rules on your registry center will not display on Dubbo Admin，and
can not be manipulated either。
