axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From German Sakaryan <>
Subject Re: Is SOAP appropriate for large data transmission
Date Thu, 22 Jun 2006 11:42:53 GMT
have tried to send large files with axis2 ?

I get fast always broken pipe exception.

German Sakaryan
Betsy Frey schrieb:
> SOAP without an attachment is inappropriate for sending large amounts of binary data,
because the XML requires it to be converted to Base64, which is inefficient.
> With an attachment, SOAP over http has the overhead of the protocol, which is not as
fast as ftp, for instance.
> I have used DIME attachments in Axis 1.1.  They worked fine up to some limit, 2gb or
so as I recall; 2 ^ 31 or 32.
> Betsy
> -----Original Message-----
> From: Rodrigo Ruiz [] 
> Sent: Thursday, June 22, 2006 2:51 AM
> To:
> Subject: Is SOAP appropriate for large data transmission
> Hi all,
> I usually read in this forum that web services and SOAP are not 
> appropriate for large data transmission, but I have never read about any 
> good technical reasons behind these sentences.
> Most of the issues I have seen in this matter are related to the SOAP 
> stack implementation, rather than to SOAP itself:
> - Progress bar for file download: You can split the download in smaller 
> chunks and transmit them using several calls. It should be possible to 
> modify the attachments implementation of SOAP and add the logic for 
> asynchronous status notification, so it is technically possible to track 
> the progress of attachments download/upload.
> - SOAP XML overhead: In fact, the overhead of a SOAP envelope containing 
> just a reference to the attachment part is more important for small 
> attachments than for large ones. Just one or two kilobytes of XML are 
> not too much when you are trying to transfer an 8GB stream.
> - Partial/broken transmissions: Again, if the attachments implementation 
> is able to track the progress of a download, it may be possible to 
> resume it after a transmission error. We would just need to be able to 
> specify the range we are interested in, just like with old plain HTML.
> Could somebody shed some light on the reasons that make SOAP 
> inappropriate for this task?
> Regards,
> Rodrigo Ruiz

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message