frereth.cp.message.constants — com.frereth/cp 0.0.5-g1ab2285

eof-error clj

eof-normal clj

header-length clj

k-1 clj

aka 1k

k-128 clj

aka 128k

k-16 clj

aka 16k

k-1f clj

k-2 clj

aka 2k

k-4 clj

aka 4k

k-64 clj

aka 128k

k-8 clj

aka 8k

k-8f clj

k-div2 clj

aka 1/2 k

k-div4 clj

aka 1/4 k

k-div4f clj

k-div8 clj

aka 1/8 k

m-16 clj

aka 16m, or 16M, or 16Mi

max-32-uint-obsolete clj

max-bytes-in-initiate-message clj

max-msg-len clj

max-outgoing-blocks clj

How many outgoing, non-ACK'd blocks will we buffer?

Corresponds to OUTGOING in the reference implementation.

That includes a comment that it absolutely must be a power of 2.

I think that's because it uses bitwise and for modulo to cope with the ring buffer semantics, but there may be a deeper motivation.

min-msg-len clj

min-padding-length clj

minute-1 clj

in nanoseconds

ms-5 clj

5 milliseconds, in nanoseconds

This almost definitely belongs in shared.constansts, assuming it isn't there already

recv-byte-buf-size clj

How many bytes from the parent will we buffer to send to the child?

sec->n-sec clj

Starting point for several values

secs-1 clj

in nanoseconds

secs-10 clj

in nanoseconds

send-byte-buf-size clj

How many child bytes will we buffer to send?

standard-max-block-length clj

stream-length-limit clj

How many bytes can the stream send before we've exhausted the address space?

(dec (pow 2 60)): this allows > 200 GB/second continuously for a year