So it is a single thread.Īs it is a long time after the ZMODEM protocol was invented, rzsz-nd starts from a basic feature, which is sending/receiving plain file in ZMODEM, without any conversion and encryption. It is a utility tool, which means it must not occupy lots of resources from the other logical server.
I have written build scripts in plain Makefile, so it is not autoconf. I have some tools on hand, the FSM and the multi-jobs Processor in C++. To get out of this dilemma, I decide to re-implement it again. And the worst thing is, this happened again and again. Sadly I gave up before I got drowned in the source code(Sorry to say that, it is my problem). Those thinking keep following me and someday I couldn’t stand for it and downloaded its source code.
Then, why do I make another implementation of it? Well, as a user, I have a lot of thinking, like what if it can blablabla or why can’t it be blablabla. It is so convenient that after I implemented the ZMODEM feature in putty-nd, I seldom use other tools to transfer files. OverviewĪs well-known, lrzsz is a very handy tool to transfer files along with the existing terminal.
