You are viewing a plain text version of this content. The canonical link for it is here.

Posted to soap-dev@xml.apache.org by Anver Sotnikov <AS...@intralinks.com> on 2001/04/18 16:52:02 UTC

Huge attachments

Current implementation of TransportMessage reads Message in memory so if I 
use SOAP to send huge attachment it fails with OutOfMemoryException. Is 
there any plans or ideas how to change it?

Re: Huge attachments

Posted by Wouter Cloetens <wo...@mind.be>.

On Wed, Apr 18, 2001 at 10:52:02AM -0400, Anver Sotnikov wrote:
> Current implementation of TransportMessage reads Message in memory so if I 
> use SOAP to send huge attachment it fails with OutOfMemoryException. Is 
> there any plans or ideas how to change it?

Lots of ideas, no concrete plans. I wish I could find my post to soap-user
about performance, suggesting a streaming strategy for reading attachment
data on both the sending and receiving end.
It would involve ripping out JavaMail etc, which is a huge effort.

bfn, Wouter