Clarifying `sub_configs` purpose about ehco

[Ehco1996]

Regarding the sub_configs feature you mentioned, indeed, starting from version v1.1.4-dev(nightly), we introduced this feature primarily to support reading proxy configurations from Clash Proxy Providers and converting them into ehco's relay configurations. This functionality is designed to enable ehco to serve as a front proxy client, providing features such as load balancing and traffic monitoring.

As for your question about introducing additional sub-configurations (such as ehco sub-configs) to split one large configuration file into several smaller ones, we are indeed considering expanding the sub_configs feature to support more flexible configuration management. We recognize that as user configurations become increasingly complex, offering more flexible ways to manage configurations will be very beneficial to our users.

Currently, the sub_configs feature is focused on integration with Clash Proxy Providers, but we are actively exploring other potential uses, including but not limited to ehco sub-configurations. Our goal is to make ehco a more powerful and flexible tool to meet our users' growing needs.

[NEK-RA]

Thanks for explanation.
Since this was quite general question, I guess this issue may be closed. Otherwise, if you would like to keep it opened for anything related in future, how should I rename it?