Hi, I'm currently looking in to convert the existing java implementation of agent module to golang considering better concurrency, performance and make it more platform enabled. Before just starting up, I'm trying to discuss which kind of changes has to be done on which end.
1) I believe we are considering to accommodate multiple agents available per controller and each agent to support multiple transports. Which means, it's a collection of agents connected to a one controller. I think this is not done yet. 2) Currently my understanding according to the implementation is that the agent module is kind of coupled with the api and controller. I feel that agent has to be an independent module. Or am I missing something? 3) The agent being independent is required for the agent to be converted to golang too. 4) I was also thinking whether the combination of transports available per agent also should be independently installable. So, that each agent could decide which transports are required. Plus they could introduce new transport plugins. (A kind of an enhancement) 5) I'm just doubt about the "LOCAL" transport. how does it work with multiple agents. According to the architecture where does the local storage exist? Is it inside the agent? Regards, Dinuka
