title: SOAP with Attachment / MIME content
body: <p>Need to send and receive a SOAP message in the following format from a third party:</p>
  
  <pre><code>POST /api HTTP/1.1 
  Host: mytesthost.com
  Content-Type: multipart/related;  
  boundary="aMIMEBoundary";  
  type="text/xml";  
  start="&lt;soap-start&gt;" 
  Content-Length: 2014 
  SOAPAction: "" 
  
  --aMIMEBoundary 
  Content-Type: text/xml; charset=us-ascii 
  Content-Transfer-Encoding: 7bit 
  Content-ID: &lt;soap-start&gt; 
  
  &lt;?xml version="1.0" encoding="UTF-8"?&gt; 
  &lt;soap-env:Envelope xmlns:soap-
  env="http://schemas.xmlsoap.org/soap/envelope/"&gt; 
  &lt;soap-env:Header&gt;
  ... 
  &lt;/soap-env:Header&gt; 
  &lt;soap-env:Body&gt; 
  ...
  &lt;/soap-env:Body&gt; 
  &lt;/soap-env:Envelope&gt; 
  
  --aMIMEBoundary 
  Content-Type: image/gif 
  Content-ID: dancingbaby.gif 
  Content-Transfer-Encoding: base64 
  Content-Disposition: attachment 
  
  &lt;Binary Data Here&gt; 
  
  --aMIMEBoundary-- 
  </code></pre>
  
  <p>Is this considered "SOAP with Attachment"? We just started looking into this and found very thin support for sending this type of message using .NET technologies.</p>
  
  <p>Please let me know if you have a starting point for this type of operation. We've looked at ServiceStack and PocketSOAP (SOAP Frameworks for .NET). </p>
  
  <p>We've also seen DIME and MTOM mentioned. Can this take the place of an SWA (SOAP with Attachment) message?</p>
  
  <p>Please let me know if you need more info. We're mainly trying to focus on sending binary data as part of a SOAP message and this is our first exposure to it. Thanks!</p>