Home >> All >> demo >> tucson

•	demo.tucson.chat.* (5)	•	demo.tucson.multimedia.* (4)	•	demo.tucson.philo.* (1)
•	demo.tucson.tictactoe.* (5)

Package Samples:

• demo.tucson.chat
• demo.tucson.multimedia
• demo.tucson.philo
• demo.tucson.tictactoe

Classes:

• PhiloRun: 5 Philosophers example using Tucson Service as coordination model with 3 prolog philosophers and 2 java philosophers. This is a concrete example of coordination among etherogenous activities. The prolog source is executed on our tuprolog virtual machine
• MasterAgent: the master agent is responsible to setup coordination specification in the tuple centre and to visualize/update the image during its distributed creation
• ChatAgent: the Chat agent acts as interface between the user and the room, in particular sending messages to room and collecting updates from the room
• ObserverAgent: The Observer Agent is responsible to observe (without polling) the chat room in order to retrieve new message appeated in the chat
• WorkerInputGUI: GUI Service used by Worker Agent to get useful inputs, such as the address of the tuple centre where the application is located
• GUI: GUI Component used by Chat Agent to get input from user and to display new messages from the room
• MainResource: install proper reactions to avoid deadlock and make chops resources avaiable to philosophers
• ChatRoom: The Chat Room setups the tuple centre, with proper specification.
• PrologPhilo: the prolog philosopher running on the tuprolog virtual machine
• WorkerAgent: the worker agent is responsible to build pieces of the image
• Gui: GUI Service used by Master Agent to display image
• JavaPhilo: the java philosopher
• User
• AgentGUI
• AgentPlayer
• UserAction
• GUIAgent
• GUIAgentApplet
• UserInterface

Home | Contact Us | Privacy Policy | Terms of Service