Why DistroProtocol does not implement APProtocol interface, and what is the intended usage of APProtocol?

[AngusYGChen]

Hi Nacos maintainers and community,

I've been deeply studying the consistency protocol architecture of Nacos recently, and I found a very interesting and confusing design that I couldn't find a clear explanation for in the official documentation or existing issues.

What I observed

1. CPProtocol has a complete implementation: JRaftProtocol properly implements the CPProtocol interface, and it is correctly initialized and managed by ProtocolManager.
2. APProtocol is an empty interface with NO implementations: The APProtocol interface extends ConsistencyProtocol but does not add any methods, and there is no class in the entire codebase that implements this interface.
3. DistroProtocol exists as a standalone class: The actual AP protocol implementation DistroProtocol does not implement any consistency protocol interface at all. It is a completely independent @Component class.
4. ProtocolManager's AP protocol initialization never runs: The initAPProtocol() method in ProtocolManager tries to get an APProtocol bean from the Spring context, but this code path is never executed because there is no such bean.
5. Naming module directly depends on DistroProtocol: The service discovery module does not use the consistency protocol abstraction layer at all. It directly injects DistroProtocol and calls its native methods like sync().

My questions

1. Is this an unfinished architecture refactoring? I know that Nacos 1.3.0 introduced the unified consistency protocol abstraction, and 1.4.0 completed the CP protocol refactoring with JRaft. Was the AP protocol refactoring put on hold for some reason?
2. What was the original design intention of the APProtocol interface? What is its intended usage if it has no implementations?
3. Why hasn't DistroProtocol been refactored to implement APProtocol? Are there fundamental incompatibilities between the Distro protocol design and the generic ConsistencyProtocol interface?
4. Does the Nacos team have any plans to complete this refactoring in future versions?
5. If Nacos ever wants to support other AP protocols (like Gossip) in the future, will they be implemented through the APProtocol interface?

This design has confused many developers who are learning Nacos's internal architecture. A clear explanation from the official team would be extremely helpful for the community to understand Nacos's design philosophy and evolution history.

Thank you very much for your time and explanation!