In the Java API, each client state has only its
messages and the message of its super client type. It
doesn't know about the other types of messages designed
for other types of clients. If the client receives a
message before it has completed a state change, or when
its in a different state, then it will be derailed and
will not be able to resync. This error only occurs
between state changes.
The solution for the moment is to have a two way
protocol that allows the client to hand shake telling
the server, that it has completely changed states
before it begins receiving messages for that state.
The code needs to be changed so that all types of
messages are processed, however only the messages that
are relavent to that type are passed up the architecture.
Log in to post a comment.
