Communications between bus are universally implemented via the superclass
GUI outbound chat messages are going to the bot, and are saved in a separate collection on the database.
Use of chat messages are not yet implemented.
The code in the gui has been cleaned however.
We need to find a way of managing bus messages. Our initial attempt is just bus to bus, layer to layer, but multiple items in the bus also have to be worked out. The busses will fill up quickly , and a layer may get many at once. This will especially an issue in a multibus system.
I think we need to get chat hooked up, sending a separate thread to the global strategy layer. This will spin of a response pipeline of 4 tickets each handled by a different agent in a different layer.
We also have some work to do on the agents, just tying them into he system. We gave the layers a superclass treatment so standing up a new agent is not difficult, but it is time consuming. They are much more heavily integrated into the bus so you have to add extra code to each to modify that.
We need to find a way of managing bus messages. Our initial attempt is just bus to bus, layer to layer, but multiple items in the bus also have to be worked out. The busses will fill up quickly , and a layer may get many at once. This will especially an issue in a multibus system.
I think we need to get chat hooked up, sending a separate thread to the global strategy layer. This will spin of a response pipeline of 4 tickets each handled by a different agent in a different layer.
We also have some work to do on the agents, just tying them into he system. We gave the layers a superclass treatment so standing up a new agent is not difficult, but it is time consuming. They are much more heavily integrated into the bus so you have to add extra code to each to modify that.