I've written a web services client for uploading images to a company using Apache SOAP 2.3.1. It works fine until the images get larger than about 4Mb at which point it starts running out of memory.

My first point is that this seems rather soon considering that there is 64Mb available by default! I can imagine there being the image binary in memory, the base64 encoded image and the soap packet.

I don't really want a limit on the size of the images that can be uploaded. I have heard that Axis will handle large files more efficiently but I'm not sure how much more. I'm also considering writing a specialized call that uses a Base64EncoderStream and writes directly to a SocketOutputStream.

Any advice on this would be greatly appreaciated. Thanks,

Barry


Reply via email to