Uses of Package
message

Packages that use message

accessControl	Access control component - Supposed to perform authentication, access and admission control.
architectureInterface	Provides all interfaces, given by this mix' software architecture for each component ("NameOfComponent"Interface.java).
inputOutputHandler	InputOutputHandler component - Handles (mix) message-based connections (see package Message) with communication partners (clients, other mixes and proxy servers) and therefore abstracts from the physic communication channels.
message	Provides different message formats, the InputOutputHandler is capable of transmitting.
outputStrategy	Output Strategy component - Collects messages until an output criterion is fulfilled (certain number of messages collected or timeout reached)

Classes in message used by accessControl

Message
Basic abstract class for all types of messages the InputOutputHandler is capable of transmitting.

Classes in message used by architectureInterface

Message
Basic abstract class for all types of messages the InputOutputHandler is capable of transmitting.

Reply
Interface, all messages must implement, that travel in direction last mix −> first mix (= receiver −> client).

Request
Interface, all messages must implement, that travel in direction first mix −> last mix (= client −> receiver).

Classes in message used by inputOutputHandler

Reply
Interface, all messages must implement, that travel in direction last mix −> first mix (= receiver −> client).

Request
Interface, all messages must implement, that travel in direction first mix −> last mix (= client −> receiver).

Classes in message used by message

BasicMessage
Interface any type of message the InputOutputHandler shall be capable of transmitting must implement.

ChannelEstablishMessagePart
Defines the message format/message parts of a ChannelEstablishMessage.

ChannelMessagePart
Defines the message format/message parts of a ChannelMessage.

ExternalMessage
Interface, all messages must implement, that involve a communication partner, that is no mix (e. g. a client or server).

InternalMessage
Interface, all messages must implement, that are sent only between the mixes of a cascade (e. g. to transmit control information between two components located on different mixes).

Message
Basic abstract class for all types of messages the InputOutputHandler is capable of transmitting.

Payload
Data structure for the "payload" of a message.

Reply
Interface, all messages must implement, that travel in direction last mix −> first mix (= receiver −> client).

Request
Interface, all messages must implement, that travel in direction first mix −> last mix (= client −> receiver).

Classes in message used by outputStrategy

Reply
Interface, all messages must implement, that travel in direction last mix −> first mix (= receiver −> client).

Request
Interface, all messages must implement, that travel in direction first mix −> last mix (= client −> receiver).