commit | 5c571952fc223f54979409bf950b159c6cbce5b2 | [log] [tgz] |
---|---|---|
author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Mon Nov 11 02:53:17 2019 +0000 |
committer | GitHub <noreply@github.com> | Mon Nov 11 02:53:17 2019 +0000 |
tree | 7dbf2bcddcb159303b7c543329945fabc35f83dc | |
parent | 9faa6a115e97fc19e83887a50073c1df5e57a994 [diff] |
Bump netty-all from 4.1.35.Final to 4.1.42.Final Bumps [netty-all](https://github.com/netty/netty) from 4.1.35.Final to 4.1.42.Final. - [Release notes](https://github.com/netty/netty/releases) - [Commits](https://github.com/netty/netty/compare/netty-4.1.35.Final...netty-4.1.42.Final) Signed-off-by: dependabot[bot] <support@github.com>
Dubbo Proxy, a gateway of Dubbo, switch from HTTP request to Dubbo protocol,then invoke Dubbo service and return to the result. Later Dubbo Proxy would combine several features, including circuit breaker, current-limiting, api management.
HTTP request format:
{application Name}/{Interface name}?version={version}&group={group}
Group and version is the mapping data in Dubbo service.
http POST body:
{ "methodName" : "sayHello", "paramTypes" : ["org.apache.dubbo.demo.model.User"], "paramValues": [ { "id": 23, "username": "testUser" } ] }
application.yml
proxy.registry.address: zookeeper://127.0.0.1:2181 #registry center address, same as Dubbo service's proxy.metadata-report.address: zookeeper://127.0.0.1:2181 #metadata center address, used by paramType search, support for dubbo 2.7 or later