Server Communication

#Server Communication

The Power TAC competition is designed as an event driven, competitive simulation, where the activity of one actor (say Broker Bob) may lead to activities of other actors (say a response of one of Broker Bob's customers).

Consequently, the Power TAC server reflects these design principles by offering a messaging framework that supports light-weight, event-driven interaction between the different core entitites of Power TAC. As shown in the figure below, two different entitites (called endpoints) are connected via communication channels which allow

Source: Spring Integration in Action, Manning

Command Objects represent the payload of messages sent between the broker agents and the server or within the server. External to internal command objects specify the possible actions of the brokers. Information sent to the brokers can be separated by public and by individual information.

For consistency we try to maintain the Naming conventions for communication channels.

Broker to TAC Server Communication

• PublishTariffCommand
• RevokeTariffCommand
• UpdateTariffCommand
• SubmitShoutCommand
• DeleteShoutCommand
• EditShoutCommand

TAC Server to Single Broker Communication

• TariffReplyCommand
• CustomerInfoCommand
• MeterReadingCommand
• DepotPositionCommand
• CashPositionCommand

TAC Server to Public Communication

• CompetitionStatusCommand
• TimeslotCommand
• WeatherDataCommand
• TariffListCommand
• CustomerInfoCommand

TAC Server internal communication

• MRSumCommand