NeverENG commented on code in PR #34: URL: https://github.com/apache/dubbo-net/pull/34#discussion_r4536979447
########## Docs/en/architecture/metadata.md: ########## @@ -0,0 +1,26 @@ +# Metadata: From Java Definitions to Invocation Signatures + +[Call-path overview](index.md) · [中文](../../zh/architecture/metadata.md) + +## Responsibility + +Metadata obtains Java interface method names, parameter types, and overload definitions, then matches caller arguments to a signature. It caches **method definitions**, not callable Provider candidates, and does not perform protocol I/O. [Registry discovery](registry.md) finds Providers, while [service selection](selection.md) maintains and selects callable candidates. + +## Loading definitions and resolving signatures + +`DubboMetadataManager` loads and caches definitions per service. Depending on Provider version and available sources, it reads from the metadata center or a short-lived Telnet `ls -l` query; Telnet can also supplement incomplete definitions. Locating a Provider may reuse registry discovery without creating a business-call driver. The metadata center can share the registry address or use a separate one. Review Comment: 已在 5f84f15 同步补到中英文 `architecture/metadata.md`:列出 `DubboClientConf.MetadataCenterAddress` / `MetadataRootPath` 的用途,并说明 Telnet 泛型类型名在用于 `$invoke` `parameterTypes` 前的 Java 类型擦除。原生协议页仍只保留线协议与连接行为。补充核对:这两项其实也已在 `README.md` / `readme_cn.md` 的配置表和元数据说明中,但你指出的 `Docs/` 内缺少入口确实存在。已检查本地文档链接和 `git diff --check`。 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
