Aias00 commented on issue #1113:
URL: 
https://github.com/apache/rocketmq-dashboard/issues/1113#issuecomment-5211312169

   Based on the current Studio model, I suggest treating `Instance.endpoint` as 
the single durable management endpoint for the first iteration rather than 
introducing a separate one-to-many Proxy-address table:
   
   - `DIRECT` instances retain a NameServer endpoint; `PROXY` instances retain 
a Proxy endpoint.
   - The Proxy compatibility endpoints should require `instanceId`, resolve the 
selected `Instance`, and reject unsupported lifecycle/config actions instead of 
falling back to process-global state.
   - A future multi-address model should be added only when the Proxy Admin 
protocol defines discovery, aggregation, and failover semantics.
   
   This keeps the current storage model backward-compatible and avoids 
persisting guessed Proxy topology before the Proxy Admin contract is available. 
I will wait for design feedback before opening an implementation 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]

Reply via email to