4.6. Messaging Service
The WAF messaging service is intended to be used as a building block for messaging applications, which are WAF applications that use messages to represent various types of communication between users.
Messages can represent an email from one user to another, or a bulletin-board post, or a comment on another object in the system. A message can store attachments such as images or other files which are relevant to the message. Each attachment can be of any arbitrary MIME type.
The implementation follows the RFC822 [1] standard, which has been deprecated by RFC2822 [2].
The Message class models a persistent text message with optional attachments:
The message body should have a MIME type of text/plain or text/html.
Each attachment to the message can have an arbitrary MIME type and format. Messages can also refer to any ACSObject on the system.
MessageParts represent a message part (an attachment) in the sense of a multipart MIME message. Each part has some content represented as an arbitrary block of bytes and a MIME type that identifies the format of the content.
A ThreadedMessage is an extension of Message that allows messages to be organized into discussion threads with a tree structure. Messages at the first level are referred to as root messages.
 | Warning |
|---|---|
If you delete the root message in a ThreadedMessage tree, all of its children are deleted. |