 
 ;;; 456-542: Loop over (range blocknum)
 ;;; (getting into details)
+
+;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
+;;; Public

The \"parent\" child/server reads/writes to pipes that this provides,
in a specific (and apparently undocumented) communications protocol.

This, in turn, reads/writes data from/to a child that it spawns.

At least, that's the impression I'm getting based on my
preliminary first few pages of the file I'm getting ready to
translate.

And then immediately after that, I think I hit the Chicago
congestion control algorithm")

;;;; Q: what's in the reference implementation?
;;;; A:
;;;; 1-66 boilerplate
;;;; 67-137 global declarations
;;;; 138-154: earliestblocktime_compute
;;;           Looks like it's finding a min
;;;; 155-185: acknowledged(start, stop)
;;;           159-167: Flag these blocks as sent
;;;                    Marks blocks between start and stop as ACK'd
;;;                    Updates totalblocktransmissions and totalblocks
;;;           168-176: Updates globals for adjacent blocks that
;;;                    have been ACK'd
;;;                    This includes some counters that seem important:

;;;                        blockfirst
;;;           177-182: Possibly set sendeofacked flag
;;;           183: earliestblocktime_compute()
      )
    ;;; No change
    state))

;;;; Q: what else is in the reference implementation?
;;;; A:

;;;; 186-654 main
;;;          186-204 boilerplate
