By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,530 Members | 2,181 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,530 IT Pros & Developers. It's quick & easy.

attachment

P: n/a
Hello:
what is the difference between soap message's attachment and soap
message's DimeAttachment,in dot net. If The web service is implemented in
different language , for example. Web service is implemented in java ,client
is dot.net,can i use dime to deal with soap attachment?Are there any
restriction exists? Addittional resource will be more helpful!!
thanks in advance!!

Nov 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
> Hello:
what is the difference between soap message's attachment and
soap
message's DimeAttachment,in dot net. If The web service is implemented
in
different language , for example. Web service is implemented in java
,client
is dot.net,can i use dime to deal with soap attachment?Are there any
restriction exists? Addittional resource will be more helpful!!
thanks in advance!!

Hello gladiator,
DIME (Direct Internet Message Encapsulation) is a W3C standard so you should not have problem using it but DIME is quite dead.
If you need to add attachments to your soap message, you can use:
1. base64 encoding
2. MTOM (Message Transimmission Optimization Mechanism)
The second method is quite young so I don't know if there are toolkits that supports it.
I think that at this moment, if you want to do something quikly (but quite dirty), the best way is to use base64 encording.
Use DIME only if you need a clean solution (using DIME you have separation from message and attachments) and you need to add multiple attachments in the same message.

For more information, look at http://msdn.microsoft.com/webservices
and for the iteroperability: http://msdn.microsoft.com/webservices/building/interop/

HTH
____________________________
Mighell (http://www.datadream.it)

Nov 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.