This is an automated email from the ASF dual-hosted git repository. wangxin pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/incubator-dubbo-website.git
The following commit(s) were added to refs/heads/asf-site by this push: new 7b273b5 build htmls 7b273b5 is described below commit 7b273b537a91edb540b7d9fe2a64025d761260cc Author: Xin Wang <xin.victorw...@gmail.com> AuthorDate: Mon Mar 25 19:41:39 2019 +0800 build htmls --- en-us/docs/user/demos/local-stub.html | 2 +- en-us/docs/user/demos/local-stub.json | 2 +- zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.html | 2 +- zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.json | 2 +- zh-cn/docs/user/demos/local-stub.html | 4 ++-- zh-cn/docs/user/demos/local-stub.json | 2 +- zh-cn/docs/user/preface/requirements.html | 2 +- zh-cn/docs/user/preface/requirements.json | 2 +- 8 files changed, 9 insertions(+), 9 deletions(-) diff --git a/en-us/docs/user/demos/local-stub.html b/en-us/docs/user/demos/local-stub.html index 24b276d..3d3c7bc 100644 --- a/en-us/docs/user/demos/local-stub.html +++ b/en-us/docs/user/demos/local-stub.html @@ -28,7 +28,7 @@ <span class="hljs-keyword">private</span> <span class="hljs-keyword">final</span> BarService barService; <span class="hljs-comment">// The real remote proxy object is passed in through the constructor</span> - <span class="hljs-keyword">public</span> (BarService barService) { + <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-title">BarServiceStub</span><span class="hljs-params">(BarService barService)</span></span>{ <span class="hljs-keyword">this</span>.barService = barService; } diff --git a/en-us/docs/user/demos/local-stub.json b/en-us/docs/user/demos/local-stub.json index 735e29f..280a4ec 100644 --- a/en-us/docs/user/demos/local-stub.json +++ b/en-us/docs/user/demos/local-stub.json @@ -1,6 +1,6 @@ { "filename": "local-stub.md", - "__html": "<h1>Local stub</h1>\n<p>When using rpc, the client usually only the interface, but sometimes the client also want to perform part of the logic in the client. For example: do ThreadLocal cache, verify parameters, return mock data when call fails., etc.</p>\n<p>To solve this problem, you can configure the stub in the API, so that when the client generates the proxy instance, it passes the proxy to the <code>Stub</code> via the constructor <sup class=\"footnote-ref\"><a href=\" [...] + "__html": "<h1>Local stub</h1>\n<p>When using rpc, the client usually only the interface, but sometimes the client also want to perform part of the logic in the client. For example: do ThreadLocal cache, verify parameters, return mock data when call fails., etc.</p>\n<p>To solve this problem, you can configure the stub in the API, so that when the client generates the proxy instance, it passes the proxy to the <code>Stub</code> via the constructor <sup class=\"footnote-ref\"><a href=\" [...] "link": "/en-us/docs/user/demos/local-stub.html", "meta": {} } \ No newline at end of file diff --git a/zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.html b/zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.html index d54768b..304b927 100644 --- a/zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.html +++ b/zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.html @@ -16,7 +16,7 @@ <p>首届Dubbo开发者沙龙在北京成功举办, 超过400位开发者参加。这是一个很好的开始!</p> <p>分享嘉宾及主体如下:</p> <ul> -<li>罗军: Dubbo 的现状现状与未来规划 <a href="https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/dubbo-present-and-future.pdf">PDF</a></li> +<li>罗毅: Dubbo 的现状现状与未来规划 <a href="https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/dubbo-present-and-future.pdf">PDF</a></li> <li>刘军: 第四届阿里中间件性能挑战赛 <a href="https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/introduction-to-4th-aliware-performance-challenge.pdf">PDF</a></li> <li>陈志轩: 通过 Dubbo 和 Spring-boot 快速构建微服务 <a href="https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/quickly-building-microservice-with-dubbo-and-springboot.pdf">PDF</a></li> <li>王欣: Dubbo 和微店的服务化实践历程分享 <a href="https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/dubbo-and-weidian's-practice-on-microservice-architecture.pdf">PDF</a></li> diff --git a/zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.json b/zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.json index 2dcc43f..1c268af 100644 --- a/zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.json +++ b/zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.json @@ -1,6 +1,6 @@ { "filename": "dubbo-meetup-beijing-may-12th-2018.md", - "__html": "<h2>首届Dubbo开发者沙龙在北京成功举办</h2>\n<p>首届Dubbo开发者沙龙在北京成功举办, 超过400位开发者参加。这是一个很好的开始!</p>\n<p>分享嘉宾及主体如下:</p>\n<ul>\n<li>罗军: Dubbo 的现状现状与未来规划 <a href=\"https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/dubbo-present-and-future.pdf\">PDF</a></li>\n<li>刘军: 第四届阿里中间件性能挑战赛 <a href=\"https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/introduction-to-4th-aliware-performance-challenge.pdf\">PDF</a></li>\n<li>陈志轩: 通过 Dubbo 和 Spring-b [...] + "__html": "<h2>首届Dubbo开发者沙龙在北京成功举办</h2>\n<p>首届Dubbo开发者沙龙在北京成功举办, 超过400位开发者参加。这是一个很好的开始!</p>\n<p>分享嘉宾及主体如下:</p>\n<ul>\n<li>罗毅: Dubbo 的现状现状与未来规划 <a href=\"https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/dubbo-present-and-future.pdf\">PDF</a></li>\n<li>刘军: 第四届阿里中间件性能挑战赛 <a href=\"https://github.com/dubbo/awesome-dubbo/raw/master/slides/meetup/201805%40Beijing/introduction-to-4th-aliware-performance-challenge.pdf\">PDF</a></li>\n<li>陈志轩: 通过 Dubbo 和 Spring-b [...] "link": "/zh-cn/blog/dubbo-meetup-beijing-may-12th-2018.html", "meta": { "title": "首届Dubbo开发者沙龙在北京成功举办", diff --git a/zh-cn/docs/user/demos/local-stub.html b/zh-cn/docs/user/demos/local-stub.html index 9ca0623..68c7b6a 100644 --- a/zh-cn/docs/user/demos/local-stub.html +++ b/zh-cn/docs/user/demos/local-stub.html @@ -23,11 +23,11 @@ </code></pre> <p>提供 Stub 的实现 <sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup>:</p> <pre><code class="language-java"><span class="hljs-keyword">package</span> com.foo; -<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">BarServiceStub</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">BarService</span> </span>{ +<span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">BarServiceStub</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">BarService</span> </span>{ <span class="hljs-keyword">private</span> <span class="hljs-keyword">final</span> BarService barService; <span class="hljs-comment">// 构造函数传入真正的远程代理对象</span> - <span class="hljs-keyword">public</span> (BarService barService) { + <span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-title">BarServiceStub</span><span class="hljs-params">(BarService barService)</span></span>{ <span class="hljs-keyword">this</span>.barService = barService; } diff --git a/zh-cn/docs/user/demos/local-stub.json b/zh-cn/docs/user/demos/local-stub.json index 523b9f1..89ce003 100644 --- a/zh-cn/docs/user/demos/local-stub.json +++ b/zh-cn/docs/user/demos/local-stub.json @@ -1,6 +1,6 @@ { "filename": "local-stub.md", - "__html": "<h1>本地存根</h1>\n<p>远程服务后,客户端通常只剩下接口,而实现全在服务器端,但提供方有些时候想在客户端也执行部分逻辑,比如:做 ThreadLocal 缓存,提前验证参数,调用失败后伪造容错数据等等,此时就需要在 API 中带上 Stub,客户端生成 Proxy 实例,会把 Proxy 通过构造函数传给 Stub <sup class=\"footnote-ref\"><a href=\"#fn1\" id=\"fnref1\">[1]</a></sup>,然后把 Stub 暴露给用户,Stub 可以决定要不要去调 Proxy。</p>\n<p><img src=\"../sources/images/stub.jpg\" alt=\"/user-guide/images/stub.jpg\"></p>\n<p>在 spring 配置文件中按以下方式配置:</p>\n<pre><code class=\"language-xml\"><span class=\"hljs-tag\"><<span class=\"hljs-n [...] + "__html": "<h1>本地存根</h1>\n<p>远程服务后,客户端通常只剩下接口,而实现全在服务器端,但提供方有些时候想在客户端也执行部分逻辑,比如:做 ThreadLocal 缓存,提前验证参数,调用失败后伪造容错数据等等,此时就需要在 API 中带上 Stub,客户端生成 Proxy 实例,会把 Proxy 通过构造函数传给 Stub <sup class=\"footnote-ref\"><a href=\"#fn1\" id=\"fnref1\">[1]</a></sup>,然后把 Stub 暴露给用户,Stub 可以决定要不要去调 Proxy。</p>\n<p><img src=\"../sources/images/stub.jpg\" alt=\"/user-guide/images/stub.jpg\"></p>\n<p>在 spring 配置文件中按以下方式配置:</p>\n<pre><code class=\"language-xml\"><span class=\"hljs-tag\"><<span class=\"hljs-n [...] "link": "/zh-cn/docs/user/demos/local-stub.html", "meta": {} } \ No newline at end of file diff --git a/zh-cn/docs/user/preface/requirements.html b/zh-cn/docs/user/preface/requirements.html index 50b8edc..81a3181 100644 --- a/zh-cn/docs/user/preface/requirements.html +++ b/zh-cn/docs/user/preface/requirements.html @@ -15,7 +15,7 @@ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/zh-cn/index.html"><img class="logo" src="/img/dubbo_colorful.png"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-switch language-switch-normal">En</span><div class="header-menu"><img class="header-menu-toggle" src="/img/menu_gray.png"/><ul><li class="menu-item menu-item-normal"><a [...] <p><img src="../sources/images/dubbo-service-governance.jpg" alt="image"></p> <p>在大规模服务化之前,应用可能只是通过 RMI 或 Hessian 等工具,简单的暴露和引用远程服务,通过配置服务的URL地址进行调用,通过 F5 等硬件进行负载均衡。</p> -<p><strong>当服务越来越多时,服务 URL 配置管理变得非常困难,F5 硬件负载均衡器的单点压力也越来越大。</strong> 此时需要一个服务注册中心,动态的注册和发现服务,使服务的位置透明。并通过在消费方获取服务提供方地址列表,实现软负载均衡和 Failover,降低对 F5 硬件负载均衡器的依赖,也能减少部分成本。</p> +<p><strong>当服务越来越多时,服务 URL 配置管理变得非常困难,F5 硬件负载均衡器的单点压力也越来越大。</strong> 此时需要一个服务注册中心,动态地注册和发现服务,使服务的位置透明。并通过在消费方获取服务提供方地址列表,实现软负载均衡和 Failover,降低对 F5 硬件负载均衡器的依赖,也能减少部分成本。</p> <p><strong>当进一步发展,服务间依赖关系变得错踪复杂,甚至分不清哪个应用要在哪个应用之前启动,架构师都不能完整的描述应用的架构关系。</strong> 这时,需要自动画出应用间的依赖关系图,以帮助架构师理清理关系。</p> <p><strong>接着,服务的调用量越来越大,服务的容量问题就暴露出来,这个服务需要多少机器支撑?什么时候该加机器?</strong> 为了解决这些问题,第一步,要将服务现在每天的调用量,响应时间,都统计出来,作为容量规划的参考指标。其次,要可以动态调整权重,在线上,将某台机器的权重一直加大,并在加大的过程中记录响应时间的变化,直到响应时间到达阈值,记录此时的访问量,再以此访问量乘以机器数反推总容量。</p> <p>以上是 Dubbo 最基本的几个需求。</p> diff --git a/zh-cn/docs/user/preface/requirements.json b/zh-cn/docs/user/preface/requirements.json index 7941a54..0e2668c 100644 --- a/zh-cn/docs/user/preface/requirements.json +++ b/zh-cn/docs/user/preface/requirements.json @@ -1,6 +1,6 @@ { "filename": "requirements.md", - "__html": "<h1>需求</h1>\n<p><img src=\"../sources/images/dubbo-service-governance.jpg\" alt=\"image\"></p>\n<p>在大规模服务化之前,应用可能只是通过 RMI 或 Hessian 等工具,简单的暴露和引用远程服务,通过配置服务的URL地址进行调用,通过 F5 等硬件进行负载均衡。</p>\n<p><strong>当服务越来越多时,服务 URL 配置管理变得非常困难,F5 硬件负载均衡器的单点压力也越来越大。</strong> 此时需要一个服务注册中心,动态的注册和发现服务,使服务的位置透明。并通过在消费方获取服务提供方地址列表,实现软负载均衡和 Failover,降低对 F5 硬件负载均衡器的依赖,也能减少部分成本。</p>\n<p><strong>当进一步发展,服务间依赖关系变得错踪复杂,甚至分不清哪个应用要在哪个应用之前启动,架构师都不能完整的描述应用的架构关系。</strong> 这时,需要自动画出应用间的依赖� ��系图,以帮助架构师理清理关系。</p>\n [...] + "__html": "<h1>需求</h1>\n<p><img src=\"../sources/images/dubbo-service-governance.jpg\" alt=\"image\"></p>\n<p>在大规模服务化之前,应用可能只是通过 RMI 或 Hessian 等工具,简单的暴露和引用远程服务,通过配置服务的URL地址进行调用,通过 F5 等硬件进行负载均衡。</p>\n<p><strong>当服务越来越多时,服务 URL 配置管理变得非常困难,F5 硬件负载均衡器的单点压力也越来越大。</strong> 此时需要一个服务注册中心,动态地注册和发现服务,使服务的位置透明。并通过在消费方获取服务提供方地址列表,实现软负载均衡和 Failover,降低对 F5 硬件负载均衡器的依赖,也能减少部分成本。</p>\n<p><strong>当进一步发展,服务间依赖关系变得错踪复杂,甚至分不清哪个应用要在哪个应用之前启动,架构师都不能完整的描述应用的架构关系。</strong> 这时,需要自动画出应用间的依赖� ��系图,以帮助架构师理清理关系。</p>\n [...] "link": "/zh-cn/docs/user/preface/requirements.html", "meta": {} } \ No newline at end of file