Stories
Slash Boxes
Comments

SoylentNews is people

Once Again on TCP vs UDP

posted by martyb on Sunday March 27 2016, @12:27PM   Printer-friendly
from the could-this-site-run-without-both-of-them? dept.

Phoenix666 writes:

Discussion on the advantages of TCP vs UDP (and vice versa) has a history which is almost as long as the eternal Linux-vs-Windows debate. As I have long been a supporter of the point of view that both UDP and TCP have their own niches (see, for example, [NoBugs15]), here are my two cents on this subject.

Note for those who already know the basics of IP and TCP: please skip to the 'Closing the Gap: Improving TCP Interactivity' section, as you still may be able to find a thing or two of interest.

It's a primer, or a refresher, or a skip. We have all kinds here. Enjoy, or don't.

Original Submission

 
This discussion has been archived. No new comments can be posted.
Once Again on TCP vs UDP | Log In/Create an Account | Top | 39 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 0) by Anonymous Coward on Sunday March 27 2016, @05:01PM

    by Anonymous Coward on Sunday March 27 2016, @05:01PM (#323570)

    udp attributes: shout. general idea/topic (of the conversation) is known. like: shine a light into a dark room -aka- the network.

    tcp attributes: argument. state-teleportation. requires duplication for operation. like:create a "light-emitting display" to show the time.

    thoughts:
    to test transmit media connection (copper, fiber, radio-waves, etc.) should use udp (how reliable is the connection? we don't know until we test. too much testing might fail the connection. be gentle); to fall-back on udp-test-confirmed reliable connection to TCP?

    both tcp and udp are "for the network". it is assumed that computers are first and foremost ALONE/singular/not-networked.
    the network-enabled program can do alot inside the payload part of tcp or udp.

    a "lazy" networked-programs relies alot on tcp/udp;

    a "smart" networked program doesn't get the "compression"
    benefit of a "lazy" program and might have to implement/duplicate
    some tcp/udp functions in the payload part ...

  • (Score: 2) by maxwell demon on Sunday March 27 2016, @06:59PM

    by maxwell demon (1608) on Sunday March 27 2016, @06:59PM (#323607) Journal

    to test transmit media connection (copper, fiber, radio-waves, etc.) should use udp

    Isn't that what ICMP is for?

    --
    The Tao of math: The numbers you can count are not the real numbers.

    • (Score: 0) by Anonymous Coward on Monday March 28 2016, @02:56AM

      by Anonymous Coward on Monday March 28 2016, @02:56AM (#323699)

      Yes but people routinely drop ICMP packets on the floor. With the DNS amplificaton attacks, UDP is becoming the next ICMP [soylentnews.org].