AbstractMessage  - AS3 BlazeDS LCDS

The body of a message contains the specific data that needs to be delivered to the remote destination.

The clientId indicates which MessageAgent sent the message.

The message destination.

The headers of a message are an associative array where the key is the header name and the value is the header value. This property provides access to the specialized meta information for the specific message instance. Core header names begin with a 'DS' prefix. Custom header names should start with a unique prefix to avoid name collisions.

The unique id for the message.

Provides access to the time stamp for the message. A time stamp is the date and time that the message was sent. The time stamp is used for tracking the message through the system, ensuring quality of service levels and providing a mechanism for message expiration.

Elementos de API relacionados

The time to live value of a message indicates how long the message should be considered valid and deliverable. This value works in conjunction with the timestamp value. Time to live is the number of milliseconds that this message remains valid starting from the specified timestamp value. For example, if the timestamp value is 04/05/05 1:30:45 PST and the timeToLive value is 5000, then this message will expire at 04/05/05 1:30:50 PST. Once a message expires it will not be delivered to any other clients.

Constructs an instance of an AbstractMessage with an empty body and header. This message type should not be instantiated or used directly.

Returns a string representation of the message.

Messages pushed from the server may arrive in a batch, with messages in the batch potentially targeted to different Consumer instances. Each message will contain this header identifying the Consumer instance that will receive the message.

Messages are tagged with the endpoint id for the Channel they are sent over. Channels set this value automatically when they send a message.

This header is used to transport the global FlexClient Id value in outbound messages once it has been assigned by the server.

Messages sent by a MessageAgent can have a priority header with a 0-9 numerical value (0 being lowest) and the server can choose to use this numerical value to prioritize messages to clients.

Messages that need to set remote credentials for a destination may also need to report the character-set encoding that was used to create the credentials String using this header.

Messages that need to set remote credentials for a destination carry the Base64 encoded credentials in this header.

Messages sent with a defined request timeout use this header. The request timeout value is set on outbound messages by services or channels and the value controls how long the corresponding MessageResponder will wait for an acknowledgement, result or fault response for the message before timing out the request.

A status code can provide context about the nature of a response message. For example, messages received from an HTTP based channel may need to report the HTTP response status code (if available).