Benson Margulies wrote:
The MTOM spec specifies the use of a subset of MIME and a subset of XOP to transmit an attachment. As Dan says, the spec probably doesn't prohibit putting a file name into the MIME header, but it also doesn't define the semantics of doing that. The spec just doesn't think about the idea of a file name associated with an attachment.
Also, the nature of MTOM is that it is an *optional* method to optimise sending of binary data. If the item is small the toolkit may well choose to transfer it as inline base64 rather than as a separate MIME part, in which case there's nowhere to put a file name. The other end shouldn't see any difference at the infoset level whether the item is transferred inline or via a MIME part.
Ian -- Ian Roberts | Department of Computer Science [EMAIL PROTECTED] | University of Sheffield, UK
