[erlang-questions] How does Erlang TCP determine the end of a TCP stream?

Eric des Courtis eric.des.courtis@REDACTED
Wed Nov 1 01:11:44 CET 2017

Then again that checksum should probably stick around with the data because
hard drives, CPUs and RAM are more likely to screw up the data.

On Tue, Oct 31, 2017 at 8:09 PM, Eric des Courtis <
eric.des.courtis@REDACTED> wrote:

> Depends on the data and what you are doing with it. If it's say a video
> over a gigantic P2P network then yes I would agree but then you might want
> something like SHA256 or SHA3 as your checksum.
> On Tue, Oct 31, 2017 at 7:31 PM, scott ribe <scott_ribe@REDACTED>
> wrote:
>> On Oct 31, 2017, at 5:05 PM, Eric des Courtis <eric.des.courtis@REDACTED>
>> wrote:
>> >
>> > I think this is probably unnecessary since an implementation for
>> something like {packet,4} is trivial to begin with so you will likely never
>> see an issue with it. Not to mention UDP and TCP both have checksums
>> checked by the OS anyway.
>> As I pointed out, you can have a bug on the sending end as well. And the
>> TCP checksum is extremely weak, basically just sum of words--that's fine
>> until you have a terribly noisy corrupt transport...
>> So yes, in a lot of circumstances it's overkill, but I prefer to be
>> paranoid when a network is involved.
>> --
>> Scott Ribe
>> https://www.linkedin.com/in/scottribe/
>> (303) 722-0567
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20171031/efb5a9a4/attachment.htm>

More information about the erlang-questions mailing list