 - DIME (Direct Internet Message Encapsulation) is a communications specification that defines a format for attaching files to Simple Object Access Protocol (SOAP) messages between application programs over the Internet. The specification was originally submitted by Microsoft and IBM. DIME is similar to but somewhat simpler than the Internet's Multi-Purpose Internet Mail Extensions (MIME) protocol.
The attached or encapsulated files in a DIME message are defined by application and are called payloads. A single message can contain payloads having multiple applications. For example, an image file, a text file, a program, and an audio file can be attached to a single e-mail message. DIME messages can be nested. That is, a payload can itself be a DIME message.
The contents of DIME messages are defined by records. Each record specifies the payload size in bytes, the payload content type, and other information. Large payloads can be broken down into smaller payloads, each with their own individual record, if necessary to accommodate the buffer capacity at the source and/or destination.
 |
Learn more about SOAP (Simple Object Access Protocol) |
| Simple Object Access Protocol (SOAP) Tutorial: This SOAP tutorial provides insight in SOAP basics, how it compares to REST, SOAP attachments and how SOAP functions with WSDL will be covered. |
| Application servers processing SOAP requests: When an application server gets a SOAP request, what namespaces/schemas does it use to parse it? Does it rely on SOAP message data or WSDL? |
| SOAP and WSDL work together: How do you use SOAP to communicate with WSDL? (i.e web services written in java) |
| REST vs. SOAP: What are your thoughts on the whole REST vs. SOAP debate? |
| Mule architect sees REST with Atom rising, UDDI fading: Dan Diephouse, the creator of XFire and software architect at MuleSource Inc., discusses the advantages in using REST and the Atom Publishing Protocol. |
| Simple Object Access Protocol (SOAP) Tutorial: This SOAP tutorial provides insight in SOAP basics, how it compares to REST, SOAP attachments and how SOAP functions with WSDL will be covered. |
| Chapter of the week: Security and Ajax: This chapter, excerpted from Ajax in Action, discusses security-related concerns that have particular implications for Ajax. |
| Chapter of the week: XML Web services: This chapter, excerpted from Core C# and .NET, takes a look at the pluses and minues of implementing and consuming Web services in a .NET environment. |
| Chapter of the week: Introduction to Web services technologies: This chapter, excerpted from Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services, focuses on the standards that make up the Web services platform and how Web ... |
| Chapter of the week: Advanced Messaging, Metadata and Security: This chapter, excerpted from Service-Oriented Architecture: Concepts, Technology, and Design, focuses on the various WS-* extensions that govern specific areas of the SOAP messaging framework. ... |
| LAST UPDATED: |
02 Sep 2003
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
 |
 |
| |
RELATED GLOSSARY TERMS
| Terms from Whatis.com − the technology online dictionary |
 |
endpoint reference
(SearchSOA.com)
An endpoint reference (EPR) is a combination of Web services (WS) elements that define the address for a resource in a Simple Object Access Protocol...
|
|
SOAP
(SearchSOA.com)
|
|
|
Show me everything on 