Rednet over redstone?

How do you figure 130 bits per second? Why wait sleep(.05) when sending and receiving? Were you aware that the other side can change the signal on his end? Thus you could simply do os.pullEvent() to block till an event came in, namely the other side sending a message that it read the bits. Then you continue sending bits.
Is sleeping more CPU intensive than os.pullEvent() or is the latter simply doing a sleep anyways?

Lastly, have you found any other implementations that let you send messages over redstone (bundled wires or otherwise)?

I've split this topic from here. You might check around to see if anyone has an old copy of the rednet API, as it used to support sending messages via bundled redstone wires. The time in between pulses is necessary as they can only propagate at a speed dependent on Minecraft's tick rate (one tick is 0.05 seconds).

Lyqyd, on 21 September 2016 - 01:01 AM said:

The time in between pulses is necessary as they can only propagate at a speed dependent on Minecraft's tick rate (one tick is 0.05 seconds).

Though from what I hear, the redstone polling rate is half that.