× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



TCP ensures that every packet sent is received in the same order that it
was sent.  At a lower level, IP performs a checksum on the data to make
sure that the data within each packet is not garbled.

So, yes...  TCP/IP will make sure that same data that was sent is also
received.

Unfortunately, this is not really "data validation".   Just because the
sent data and the received data matches doesn't mean that this data is
"correct".  The sending program could have a bug.  The receiving program
could have a bug.   The data could have gotten corrupt on disk on one
side or another...   reasons why the data could be invalid are many :)

So, I would never advise against a check-digit.   It's not nearly as
robust a mechanism for ensuring data integrity as that used by TCP, but it
may validate your record layout in a way that TCP can't even understand...

Of course, it's your call...

On Tue, 29 Jan 2002, DeLong, Eric wrote:
>
> Group,
>
> I got a q+d project this morning to write a socket client app.  The
> programmer at the other end wants to include a check digit to validate the
> record before processing.  I always thought TCP handled all data validation,
> eliminating the need to add this layer of validation.  He claims that bad
> data and/or garbled records will still sometimes be returned to the
> application, making this additional testing and process control necessary.
> I have doubts.  Can anyone confirm that this is necessary, or even useful?
> TIA.
>
> Eric DeLong
> Sally Beauty Company
> MIS-Sr. Programmer/Analyst
> 940-898-7863 or ext. 1863
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.