He might be talking about jabber xmlstream. Yeah I do agree encapsulating the file in an xml could introduce overhead (I remember doing this in my former company where the file in encoded in base64). Why don't you just transfer the file via http/ftp? Send an xml to the client containing the address of the file and let the client application do the fetching.
<br><br><div class="gmail_quote">On Nov 28, 2007 2:24 AM, Atilla <<a href="mailto:theatilla@gmail.com">theatilla@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Are you referring to ActionScript's XMLSocket or just some generic TCP<br>connection that expects XML to be transferred over it? Are you<br>communicating with something existing and if not - why do you need to<br>use XML-based communication to transfer a file?
<br><br>Unless there is some specified format, you can transfer it any way you<br>find convenient, just make sure you think of the corner cases and the<br>size of the file. Some XML parsers will not be happy if they have<br>
elements with huge inner data nodes. I guess encapsulating all the<br>file's details in XML elements would be enough. Send the filename,<br>file size, a digest of the file for verification and/or debugging,<br>(the usual md5 should do the trick) and the file content itself,
<br>encoded in a convenient way - say with base64. Mind that this will<br>have additional overhead when transferring the file.<br><div><div></div><div class="Wj3C7c"><br>_______________________________________________<br>
Twisted-Python mailing list<br><a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br><a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
</a><br></div></div></blockquote></div><br>