NeverENG commented on code in PR #34:
URL: https://github.com/apache/dubbo-net/pull/34#discussion_r4510754442


##########
CHANGELOG.md:
##########
@@ -0,0 +1,17 @@
+# Changelog / 变更索引
+
+This file is a Git index, not a second implementation history. Each link below 
resolves to a merged PR or Git object; source and tests remain the authority 
for current behavior. For usage, see the [English README](README.md) or [中文 
README](readme_cn.md); for code-reading routes, see 
[English](Docs/en/architecture/index.md) and 
[中文](Docs/zh/architecture/index.md). Design rationale belongs in the [RFC 
convention](Docs/en/rfc.md) and future decision-specific RFCs.
+
+本文件只提供 Git 索引,不重复编写实施过程。下列链接均指向已合并 PR 或 Git 对象;当前行为仍以源码和测试为准。使用说明参见英文或中文 
README,读代码从中英文代码地图进入,架构取舍参见 [RFC 约定](Docs/zh/rfc.md)。
+
+## Unreleased / 未发布
+
+**No release is asserted here.** The project file declares a package version, 
but that alone is not a verified Git tag or published release. The [comparison 
since the import 
merge](https://github.com/apache/dubbo-net/compare/e10f6d50e97e15bb1164da3c8beccc2380534db5...main)
 is a moving view of `main`, not a release boundary. When a real tag or release 
exists, add its verified link and a short user-visible summary; do not relabel 
these entries as a historical release.
+
+**此处不声明已经发布。** 项目文件中的包版本号不能单独证明 Git tag 或 Release 已发布。[导入合并后至 main 
的比较视图](https://github.com/apache/dubbo-net/compare/e10f6d50e97e15bb1164da3c8beccc2380534db5...main)会随
 `main` 变化,不是发行版本边界。将来有可核验的 tag/release,再补链接及简短的用户可见摘要,不倒填虚构版本。
+
+- Import provenance / 导入来源:[PR 
#1](https://github.com/apache/dubbo-net/pull/1), [merge 
commit](https://github.com/apache/dubbo-net/commit/e10f6d50e97e15bb1164da3c8beccc2380534db5).
 The import working notes are not the current code guide / 导入工作记录不是当前代码指南。

Review Comment:
   已在 e2de98f 新增精简的 `Docs/import-status.md`,保留 
LICENSE/MIT、SGA/ICLA/IP-clearance 待核事项及当时外网验证失败的边界;CHANGELOG 链到此页,不宣称合规已完成。



##########
Docs/en/architecture/index.md:
##########
@@ -0,0 +1,51 @@
+# Source Navigation: Calls and Updates
+
+[Documentation home](../index.md) · [中文](../../zh/architecture/index.md) · 
[User guide](../../../README.md)
+
+This map describes the **current `main` source used by PR #34**, not a 
proposed architecture. DubboNet is a consumer of remote Java Providers. The two 
paths below can be read independently; conditional steps do not run on every 
request. For API usage, start with the [user guide](../../../README.md); wire 
details belong to the [native](../protocols/native-dubbo.md) and 
[Triple](../protocols/triple.md) pages.
+
+## Request path: `QueryAsync` to result
+
+```text
+DubboClient.QueryAsync
+  ├─ Java types missing → CreateMetadataInvocationAsync → DubboMetadataManager 
→ signature resolution
+  └─ QueryInternalAsync → GetRequiredProtocolAsync (best-effort overload check)
+       → DubboDriverCollection.GetDubboActuatorSuite(reserve: true)
+          ├─ no driver → ConcurrentGetProviderEndPoints → 
AddDubboServiceDriver → select again
+          ├─ driver with no Providers → discover again; retry only if 
Providers appear
+          ├─ candidates present but no available actuator → failure result
+          └─ selected → LoadBalancedInvocation.InvokeAsync → actuator 
SendQuery → DubboRequestResult
+```
+
+| Start reading here | Question and next page |
+| --- | --- |
+| [`DubboClient.QueryAsync` / 
`QueryInternalAsync`](../../../Clients/DubboClient.cs) | Where do arguments 
enter? When are types inferred, protocol checked, and initial discovery 
triggered? → [Client](client.md) |
+| [`CreateMetadataInvocationAsync`](../../../Clients/DubboClient.cs) / 
[`DubboMetadataManager.GetServiceMethodsAsync`](../../../Clients/DubboMetadataManager.cs)
 | Where do Java signatures come from, and what if they are unavailable? → 
[Metadata](metadata.md) |
+| [`ConcurrentGetProviderEndPoints` / 
`GetSeviceProviderEndPointsAsync`](../../../Clients/DubboClient.cs) | Who looks 
up addresses and installs subscriptions? → [Registry and 
discovery](registry.md) |

Review Comment:
   已在 e2de98f 同步中英文源码路径、方法名及状态归属表,对照 #36 head 9809cea 的源码验证。定下顺序:先合并 #36,再合并 
#34;#34 先合并会产生临时死链,已在两份 PR 描述中标明不可提前合并。合并前还要对实际落地主干复核。



##########
Docs/en/architecture/index.md:
##########
@@ -0,0 +1,51 @@
+# Source Navigation: Calls and Updates
+
+[Documentation home](../index.md) · [中文](../../zh/architecture/index.md) · 
[User guide](../../../README.md)
+
+This map describes the **current `main` source used by PR #34**, not a 
proposed architecture. DubboNet is a consumer of remote Java Providers. The two 
paths below can be read independently; conditional steps do not run on every 
request. For API usage, start with the [user guide](../../../README.md); wire 
details belong to the [native](../protocols/native-dubbo.md) and 
[Triple](../protocols/triple.md) pages.

Review Comment:
   已去掉两种语言中的 PR #34/main 限定,改为“当前实现”,以源码及测试为准(e2de98f)。



##########
Docs/en/code-map.md:
##########
@@ -0,0 +1,5 @@
+# Code map moved
+
+The [source-reading route](architecture/index.md) is now at 
`Docs/en/architecture/index.md`. This page only preserves existing links; 
future content belongs in the architecture overview and topic pages.

Review Comment:
   已删除三个在 main 上从未存在过的伪兼容页,并修正 PR 描述;仅保留真实旧协议路径的入口(e2de98f)。



-- 
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]

Reply via email to