1. Message Format

2. - Message format
The Internet message format is now defined by RFC 5322, with multi-media content attachments being defined in RFC 2045 through RFC 2049, collectively called Multipurpose Internet Mail Extensions or MIME. RFC 5322 replaced the earlier RFC 2822 in 2008, and in turn RFC 2822 in 2001 replaced RFC 822 – which had been the standard for Internet for nearly 20 years. Published in 1982, RFC 822 was based on the earlier RFC 733 for the ARPANET.

3. Specific Area Message Encoding - Full message format
There is one second of blank audio between each section, and before and after each message. For those used to packet communications systems where each packet has a checksum, note that there is no checksum used in the message format. Each message is supposed to be transmitted 3 times, and the receiver is obliged to implement columnar parity correction.

4. SOAP - Message format
For example, CORBA, GIOP, ICE, and DCOM use much shorter, binary message formats

5. Action Message Format
'Action Message Format' ('AMF') is a binary format used to serialize object graphs such as ActionScript objects and XML, or send messages between an Adobe Flash client and a remote service, usually a Adobe Flash Media Server|Flash Media Server or third party alternatives. The Actionscript 3 language provides classes for encoding and decoding from the AMF format.

6. SOAP (protocol) - Message format
For example, CORBA, General Inter-ORB Protocol|GIOP, Internet Communications Engine|ICE, and Distributed Component Object Model|DCOM use much shorter, binary message formats

7. For More Information, Visit:
The Art of Service