cz.cuni.amis.pogamut.ut2004.communication.translator.bot.state
Class HandshakeControllerState
java.lang.Object
cz.cuni.amis.pogamut.ut2004.communication.translator.bot.support.AbstractBotFSMState<InfoMessage,TranslatorContext>
cz.cuni.amis.pogamut.ut2004.communication.translator.bot.state.HandshakeControllerState
- All Implemented Interfaces:
- IFSMState<InfoMessage,TranslatorContext>
public class HandshakeControllerState
- extends AbstractBotFSMState<InfoMessage,TranslatorContext>
This state is introduced because start/end messages of the list of item categories, mutators, navpoints and players.
Without this state we would have difficulties with switching between MutatorListState -> PlayerListState -> etc...
As there is always: ... list ... END_MSG NEW_START_MSG ... list ... the problem lies withing END_MSG and NEW_START_MSG.
On END_MSG we will switch to this state and on NEW_START_MSG we will switch to the state that will handle appropriate
incoming list.
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait |
HandshakeControllerState
public HandshakeControllerState()
init
public void init(TranslatorContext context)
restart
public void restart(TranslatorContext context)
stateEntering
public void stateEntering(TranslatorContext context,
IFSMState<InfoMessage,TranslatorContext> fromState,
InfoMessage symbol)
stateLeaving
public void stateLeaving(TranslatorContext context,
IFSMState<InfoMessage,TranslatorContext> toState,
InfoMessage symbol)
stateSymbol
public void stateSymbol(TranslatorContext context,
InfoMessage symbol)