Not sure why you'd need MIME support. But WSE supports DIME (essentially
mime/attachments for web services). So you can send attachments but
stuffing them in the soap context. This [0] article should have pointers
on how do get that done
[0] -
http://www.codeguru.com/Cpp/I-N/internet/webservices/article.php/c8691__3/
> Quick question:
>
[quoted text clipped - 8 lines]
> operate at the SoapHTTPClientProtocol level, while I'd like to keep
> the lower-level access provided by SoapClient.

Signature
HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dilip.krishnan AT apdiya DOT com
Luca Lettieri - 18 Apr 2005 09:55 GMT
> Not sure why you'd need MIME support. But WSE supports DIME (essentially
> mime/attachments for web services). So you can send attachments but
Unfortunately, I need MIME; specifications which I can't touch require
compliance with the SwA model.
If I can't find the implementation, I could write it myself. The usual
way would be to declare a SoapExtension and override the various
serialize and deserialize methods, then hook the extension either by
assigning the attribute to the client methods or via the .config file.
The problem is that, as far as I know, the hooks work with proxies
derived by the SoapHTTPClientProtocol structure; is there any way of
using this with the WSE infrastructure and the SoapClient class?