I guess it depends on how large the data. IIRC, MTOM still requires the
*whole message to be loaded (at the client receive side) in memory before
you can process it and you can not chunk receives at the client . It also
adds ~33% to the size because of the base64 encoding. So in this regard, it
really is not much different then base64 encoding a byte[] and sending a
very large string in the reply yourself. I would welcome correction if my
understanding is not right. If files are really large, the OP may be better
off chunking them manually or using Sockets.
--
William Stacey [MVP]
"Steven Cheng[MSFT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
| Hi Asaf,
|
| Not sure what's the "files" you mentioned here.
|
| "but I prefer not to use files to transfer data."
|
| As for MTOM, it is just a binary data encoding pattern which can help
| effeciently compressed and embed binary data in XML webservice soap
| message. And it won't matter whether your data is comming from a file or
| just a binary data block. You can just define your webmethod's parameter
or
| return value as byte[] and configure your client/server WSE 3.0 enabled
| application to send or recieve data encoded through MTOM:
|
| #How to: Send and Receive Large Amounts of Data to and from a Web Service
|
http://msdn.microsoft.com/library/en...4e4-4056-906d-
| 72504ed8c0df.asp?frame=true
|
| Regards,
|
| Steven Cheng
| Microsoft Online Support
|
| Get Secure!
www.microsoft.com/security
| (This posting is provided "AS IS", with no warranties, and confers no
| rights.)
|