William > Martin, the most reliable means of detecting corruption is to use some > kind of cryptographic hash; this is pretty much standard in EDIINT and > ebXML messaging services. The error correction protocols in the > underlying transport method also ensure that information isn't garbled. > To the best of my memory, we haven't seen many of the garbled > transmissions you're talking about when using TCP/IP protocols like > HTTP, SMTP and FTP. And what few "garbles" we've encountered have mostly > been a mismatch between character sets. What the heck are you using that > this is a significant problem? I don't even think I've had that many > problems with Kermit!!
Once every two years, over a significant number of customers, adds up to a high frequency. Documents with internal numbering (eg. ASNs and HL levels) make it easy to find. I've seen the problem receiving from Sterling, where the data on the server was correct, but on the client's machine it was missing a block of data. With more people handling the data due to multiple interconnects, it's sometime difficult to find out where the problem happened, but it _does_ happen. Now that many of the trading partners have penalties for incorrect transmissions, there is a strong onus on the senders to prove their 'innocence'. > Nevertheless, I'll add this "deficiency" of XML (or rather is it a > deficiency of your communications protocols?) to the list. It has nothing to do with XML in particular, but due to the underlying protocols. Earl Wertheimer [EMAIL PROTECTED] http://www.spe-edi.com . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
