Some tests the folks working on the Atom standard did showed that you get an average of 1.6% inflation doing a base64 encoding after compression, so its not so bad with moderately sized chunks of data and does confer some advantages when the data is within the transferred xml document. Base64 is suboptimal when working with large chunks of data with minimal redundancy. Also not good when working with embedded devices or those with limited or expensive bandwidth, but ok for client-server transactions over the wire. -- Andy
>>> [EMAIL PROTECTED] 01/07/05 10:59AM >>> I have to add one comment: Base64 encoding might still compress well, so if you can enable compression support for the client and server, you might be able to use the simplest approach without feeling too bad about using up the world's dwindling bandwidth resources. Another thing you might want to consider is also that some servers have a limit on the content-length of posted data: in ASP.NET it's 4Mb by default - not so much. HTH Patrick -----Original Message----- From: Tardif, Sebastien [mailto:[EMAIL PROTECTED] Sent: 07 January 2005 17:44 To: [EMAIL PROTECTED] Subject: RE: Best way to send attachments You have to differentiate between the representations made in a specific language of the attachment than the way the attachment is sent. By playing with some flag you can see an attachment in Java as a DataHandler, a byte[], or Image or many others. However they can all be transfered in the same way and the other end of the communication can use a different representation. In Axis you can send the attachment using: * SwA * DIME * xsd:base64Binary The other end has to understand those Web Services standard. For example .NET doesn't know about SwA. All implementation know about xsd:base64Binary. If your attachment are big you don't want or cannot use xsd:base64Binary because it doesn't stream well and takes 33% more bandwidth than SwA or DIME. -----Original Message----- From: Praveen Peddi [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 11:43 AM To: [EMAIL PROTECTED] Subject: Best way to send attachments Hi team, I did lot of research on Axis attachments but I am still not able to figure out the best way to send attachments. We currently use DataHandler which works fine with Java clients. But The requirement is to support non-java clients also. And I read that DataHandler does nto work with non-Java clients. Can anyone clearly explain how to implement attachments using Axis server so that it can work with non-java clients. If you have a working sample, that would be really great! Thanks Praveen ************************************************************** Praveen Peddi Sr Software Engg, Context Media, Inc. email:[EMAIL PROTECTED] Tel: 401.854.3475 Fax: 401.861.3596 web: http://www.contextmedia.com ************************************************************** Context Media- "The Leader in Enterprise Content Integration"
