ynniv on Nostr: Sorry, my internet comparisons aren't helping. You said that you're doing this: T: ...
Sorry, my internet comparisons aren't helping. You said that you're doing this:
T: Connection
R: ack
T: ready
R: ready ack
T: request to send
R: ready
T: Note1
R: ack
T: Note2
R: ack
T: final done
R: done ack
I'm suggesting:
T: Ready to send
T: Note1
T: Note2
T: ErrorCorrectionA
T: Maybe: ErrorCorrectionB
T: Done
R: Maybe: request to resend partN
R: Done ack
So, half as many packets, no channel downtime, and the possibility of many receivers. This is the difference between "TCP" and "BitTorrent". I don't it's incompatible with your hardware goals
T: Connection
R: ack
T: ready
R: ready ack
T: request to send
R: ready
T: Note1
R: ack
T: Note2
R: ack
T: final done
R: done ack
I'm suggesting:
T: Ready to send
T: Note1
T: Note2
T: ErrorCorrectionA
T: Maybe: ErrorCorrectionB
T: Done
R: Maybe: request to resend partN
R: Done ack
So, half as many packets, no channel downtime, and the possibility of many receivers. This is the difference between "TCP" and "BitTorrent". I don't it's incompatible with your hardware goals