I'm trying to learn about SOAP and related technologies. I have recently been working on a connected wire protocol which involves sending XML messages to and from client and server. Most of it is a request-response system with the occasional unsolicited server->client message. Each message is wrapped in a pre-defined XML envelope. Sounding a bit like SOAP to anyone? So, I'm interested in how I can replace part of this system with SOAP.
So, here's how it went in tonight's web info-quest:
I'm using microsoft technology to start with: .NET to .NET.
In the future, I will need to send binary files from the client to the server (data for transmission). Therefore I'm also looking for neat ways to send both XML messages and the occasional bit of binary data.
I started out by noticing something about DIME somewhere. Back to MSDN →
Sending Files, Attach,ments, and SOAP Messages Via Direct Internet Message Encapsulation,
Understanding DIME and WS-Attachments - sounds good, but the article is really old (ok, really old in Web Services terms).
Google for DIME and Indigo (Indigo is Microsoft's up and coming web services stack stuff, so it's a good term to see if DIME is no longer loved) → DIME is dead PASWA/MTOM is the way to go (ah-ha!) → Back to MSDN →
Messaging Specifications Index Page → XML, SOAP, and Binary Data:
Hmm, no concrete evidence of an implementation. Back to Google →
Hmm. This leaves me confused. Dime is dead, MTOM is the way forward. Only it doesn't seem that anybody has bothered to create MTOM yet. What's a developer to do?
Update: It seems that in WSE 2, Microsoft are abstracting attachments from the DIME-specific to more general attachments so that migration to MTOM will be less painful: Philip Rieck.Posted by Simon at March 2, 2004 09:46 PM | TrackBack