Most implementations tend to choke on large http transfers because they tend to buffer the entire transmission prior to sending. Usually done under the assumption you are transfering single web pages and not large files.
We've have fairly good results at sending large (>1G) attachments through axis. This was done using chunked-encoding and redirecting the axis attachment directory per attachment to avoid recopying data into a final location. Although when dealing with large attachments, you should consider implementing some type of checkpointing during the transfer in case of failure.
-Mike
On Thu, 7 Apr 2005, THOMAS, JAI [AG-Contractor/1000] wrote:
More than Axis, it would be a problem with HTTP assuming you are using http transfer. HTTP has a limitation on size that varies slightly by implementation but from experience, anything over 10meg would be a problem.
Jai
-----Original Message----- From: Alex Milanovic [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 4:33 PM To: [email protected] Subject: sending very large attachments
Hi All, I was wondering if it would make sense to use the SOAP attachment method for sending very large files from one host to another over the Internet? How would AXIS deal with a file of 1GB in size? Alex
