Entering the mosh pit
Entering the mosh pit
Posted May 17, 2017 17:24 UTC (Wed) by shemminger (subscriber, #5739)In reply to: Entering the mosh pit by obonaventure
Parent article: Entering the mosh pit
"Those who do not understand TCP are doomed to reinvent it"
Posted May 17, 2017 21:24 UTC (Wed)
by itvirta (guest, #49997)
[Link]
Perhaps, but it does have the advantage that it works without any kernel support.
In mosh's case, it also has the upside that it knows more about the underlying data
Posted May 17, 2017 22:42 UTC (Wed)
by renox (guest, #23785)
[Link]
Posted May 17, 2017 23:02 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link] (1 responses)
So it's much better to transmit the whole screen state anew if an update packet is lost rather than wait for TCP retries to deliver all the intermediary packets.
For the same reason voice/video conferences use UDP - it's better to simply drop a small update to compensate for it later rather than cause the whole screen to stutter while the stream recovers.
>"Those who do not understand TCP are doomed to reinvent it"
Posted May 20, 2017 7:28 UTC (Sat)
by niner (subscriber, #26151)
[Link]
Entering the mosh pit
Which helps a lot in getting your software to work across different operating systems.
than a general purpose stream transmission algorithm does. Namely, changes to the
screen can be mercilessly discarded when the client isn't looking.
Entering the mosh pit
For example I hate having to type sleep 30 to prevent me from trying "too soon" to restart an application which then fail because the TCP connection fail.
Entering the mosh pit
Nope. Mosh is essentially a media application - it transmits the live video of the remote terminal.
Those who think that TCP is The Answer are foolish in the extreme.
Entering the mosh pit
