Package ks.protocol

All commands and messages that are sent/received by the client and server must be available to both sets of components.

See:
Description

Class Summary

BulkLoginMessage	Login Message sent on login that contains full set of all active users.
ChatCommand	Represents a command to send text to all players on a table.
CreateCommand	Class to represent the command to create a table.
FingerCommand	Return information about the specific user.
GameOverCommand	Class to represent the ending of a table at a client.
JoinCommand	Class to represent the command to join a table.
LeaveTableCommand	Class representing the command to leave a table.
LogoutCommand	The command requesting cline to logout of to the system.
OutputCommand	Class to represent output to be sent from one client to another via the Server.
PlugInManagerCommand
PlugInManagerMessage	Messages to plugin Manager on client side.
ProtocolCommand	Represents the initial command from the client in its earliest communication with the server.
RejoinCommand	Class to represent the command to rejoin a table.
ShoutCommand	Represents a text message 'shouted' to the entire lobby.
TableManagerCommand	Class to represent a command sent to the TableManager.
TablesCommand	Represents the command to list active tables.
TellCommand	Represents the command for sending a private message to another user in the main lobby.
UserManagerCommand	Class to represent a command sent to the UserManager.
UserManagerMessage	Base class for all usermanager messages.
WhoCommand	Command to get full list of all users registered for the system.

Package ks.protocol Description

All commands and messages that are sent/received by the client and server must be available to both sets of components. This package contains the full set of commands and messages that are not pre-defined within the KS hierarchy. This package may contain the definition of more commands and messages than may actually be needed within a given configuration of components. The essential point is that each of these commands and messages has been published and will never change; they are immutable. If a change is needed, then we will need to institute some versioning scheme, and I am not ready to contemplate going in that direction. Instead of changing the classes in this package, we will introduce additional classes as needed.