Oxidaner opened a new issue, #1579:
URL: https://github.com/apache/dubbo-admin/issues/1579

   Parent: #1491
   
   Phase 4 (part 2) — registry-backed generic invocation for the `dubbo` and 
`tri` protocols.
   
   ### Scope
   
   - Registry-backed generic client built on `GenericService.Invoke(method, 
parameterTypes, args)` for `dubbo` and Triple non-IDL unary calls.
   - Long-lived generic client/reference reused per discovery and service 
identity.
   - Protocol/timeout/error mapping for both protocols.
   
   ### Acceptance criteria
   
   - Invocation goes through the normal Dubbo directory and router. Admin does 
not implement a second load balancer and never connects directly to a specified 
provider URL.
   - Provider selection is delegated to dubbo-go.
   - `fail-fast` with `retries=0`: one `tools/call` issues **at most one** RPC 
attempt.
   - After the RPC has been dispatched, a timeout or a dropped connection 
returns `unknown-outcome` — no provider switching and no protocol fallback 
retry, because the original call may already have executed successfully.
   - The protocol actually exported by the service is enforced: selecting a 
protocol the service does not export is rejected at publish time with an 
explicit reason.
   - Error contracts are defined per protocol and documented; the `tri` error 
path is known not to carry the Java cause chain or stack trace.
   - A context deadline is always created for `tri` as the primary timeout 
guarantee.
   
   ### PR
   
   PR-6 — generic client, protocol/timeout/error mapping.
   
   Dependency: Phase 2 (PR-2) and Phase 1.
   
   Detailed design: [proposal §15 (line 
1243)](https://github.com/Oxidaner/dubbo-admin/blob/213bd38dbcfbe0c5bac64c7c8b949651f1633ca9/docs/proposal/mcp-server-proposal.md?plain=1#L1243)
 — design PR #1541.
   


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