this post was submitted on 06 Jan 2024
174 points (97.8% liked)
Asklemmy
43953 readers
801 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It was an evolution of previous protocols and only marginally better/faster than, say, ymodem.
It was useful, but was it really ahead of its time?
Hmmโฆ I remember zmodem being noticeably faster, more reliable, and flexible compared to its predecessors. But I think of it as ahead of its time inasmuch as what followed seemed a definite step back. Internet-based protocols which replaced it were quite a bit slower due to latency issues and what not, and it would take quite some time for new approaches to surface. Today, we have the like of bittorrent which does leap ahead in many ways but that was a long time coming.
Technically speaking, it wasn't replaced by IP-based utilities, since they have different functions. Zmodem is intended for sending binary files over an ASCII-based (7-bit) serial line, whereas the Internet-based protocols send files over IP, which is a packet-based networking protocol. That's where the performance difference comes in, since TCP/IP has significant overhead in the form of TCP and IP headers in each 1500-byte packet, plus extra processing costs on each end. That overhead brings with it far more flexibility in connecting to any arbitrary host on the network to transfer files, not just the two on either end of a serial line.
(It wasn't even replaced, since it's still available on my computer right now, installed as a dependency of something or other. I think the last time I used it was to transfer a file to an embedded device.)
Probably incremental, but I'll tell you this: I certainly remember the benefit of ZMODEM-90 with MobyTurbo over YMODEM-g.
I haven't thought of that protocol feature in about 20+ years. Saved so much extra time transferring over long-distance ($$$).
Just a casual reminder that 20 years ago is 2004. Not trying to correct you or anything, just sharing in the existential dread I felt reading this.
Yep, 2004 is about right, going through terminal emulators and reminiscing on old protocols that no longer mattered because of broadband and TCP/IP. Time flies, that's for sure.
i think zmodem would resume/reattempt when transfers started to fail or drop.
Xmodem and ymodem would do some retries. But xmodem specifically allowed resuming. And the ability for terminals to auto-downlpad if they got a particular byte sequence