Re: Serial (rs232 etc.) to IP



On 2005-10-27, Ignacio G.T. <igtorque.remove@xxxxxxxxxxxxxxx> wrote:

>> If you are using a protocol that was initially written for serial line
>> communication with normal CRC checks and timeout controls, why bother
>> with TCP, just use simple UDP. If the UDP frame is lost, let the
>> original serial line protocol timeout mechanism handle any missing
>> data.
>
> This has at least one problem: these serial line protocols usually
> assume that packets arrive in order.

And unduplicated. I see duplicate packets not infrequently on
my home wireless network, but I don't ever remember seeing
out-of-order packets (though I've never specifically looked for
them either).

> This makes sense for these protocols (I cannot imagine a
> message jumping over the previous one and reaching its destiny
> sooner than the other), but not for IP packets.

Any decent serial protocol would deal with out-of-order or
duplicated packets, but there are a lot of indecent protocols
in use.

--
Grant Edwards grante Yow! I'm rated PG-34!!
at
visi.com
.



Relevant Pages

  • TCP/IP Applications FAQ
    ... waiting for an ICMP Echo Reply from the host. ... Each trio of packets 'expire' at a succeeding ... Of the rexec protocol. ...
    (comp.unix.questions)
  • TCP/IP Applications FAQ
    ... waiting for an ICMP Echo Reply from the host. ... Each trio of packets 'expire' at a succeeding ... Of the rexec protocol. ...
    (comp.unix.questions)
  • TCP/IP Applications FAQ
    ... waiting for an ICMP Echo Reply from the host. ... Each trio of packets 'expire' at a succeeding ... Of the rexec protocol. ...
    (comp.unix.questions)
  • TCP/IP Applications FAQ
    ... waiting for an ICMP Echo Reply from the host. ... Each trio of packets 'expire' at a succeeding ... Of the rexec protocol. ...
    (comp.unix.questions)
  • TCP/IP Applications FAQ
    ... waiting for an ICMP Echo Reply from the host. ... Each trio of packets 'expire' at a succeeding ... Of the rexec protocol. ...
    (comp.unix.questions)