NeverENG commented on code in PR #34: URL: https://github.com/apache/dubbo-net/pull/34#discussion_r4513682669
########## 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: 更正前一条回复:你指出的临时死链风险确实存在,不能只靠规定 #36 先合并来规避。已在 eab4c86 将 #34 中英文架构页恢复为当前 main 真实存在的路径、方法和状态归属,并对当前 main 校验本地链接及方法入口。新顺序是 #34 先合并,#36 随后在其 PR 内同步文档,再合并 #36;两份 PR 描述已更正。 -- 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]
