RE: http Post with Large Files

[Gary Koepnick <gary@xxxxxx>]

Our company sends thousands of messages a day ranging in size from a few K 
to a few Meg and we have NEVER had a problem using smtp. I can also look at 
our server and literally watch the connection being made with the recipients 
server and the completion of the transaction. Also, if properly configured 
on both ends instant delivery notification can be done. The only issue with 
smtp is the possibility of the transactions getting out of order.

I am curious, what smtp server software were you using that was unable to 
handle large files?


>> One of the main reasons http was selected by the gas industry is that
>> smtp cannot handle large files well, while http post sends large files
>> effectively.  We pilotted last summer, and sent files in the 40k range
>> with no problem.  We also transmitted 3 meg files routinely with no
>> issues.  We sent 30 meg successfully, although some sites experienced
>> problems with their cgi's or their low-speed connections; not a problem
>> with the protocol.
>>
>> We are in production with EDI via http post, and it works quite well.
>> Most EDI files are < 40k.  The industry group felt it could not afford
>> smtp for EDI due to the lack of instant notification of receipt, the
>> inability to handle large files and the possibility of "last-out, first
>> in"(i.e., receiving files out of order).  Our business demands immediate
>> response to large $, time sensitive transactions -- ftp or http were the
>> only choices to support this.
>>
>> Regards,
>> Diane Biegel
===== Comments by GARY@ldcorp (Gary Koepnick) at 6/24/97 10:38 am


Regards,

Gary S. Koepnick
Gkoepnick@xxxxxx

Loren Data Corp.
http://www.ld.com