7698b9fb81
do not rely on unspecified Go behaviour; fix TCP ring buffer bug ( #16 )
...
* do not rely on unspecified Go behaviour; fix TCP ring buffer bug
* even more stricter error handling on tcp connections
* stricter lock copying in tcp.Conn, even though likely not a problem
* add listener and tcp pool logging
* forgot reqAddr unused
* add logging to TCPConn and friends
2026-01-05 10:03:24 -03:00
f5157e7e4a
huge fixes to ring buffer implementations and mostly passing tests
2025-11-05 19:21:30 -03:00
5e5f21a2b8
rethinking ring buffer semantics and breaking everything in the process
2025-11-05 02:35:53 -03:00
6a30268f83
done for today :)
2025-01-26 19:02:16 -03:00
94c59ee84e
segment Ring tests more: add TwoWrite,Empty,NonEmpty
2025-01-26 12:19:29 -03:00
c9aca77641
more defined semantics for low level Ring buffer indices
2025-01-26 10:37:04 -03:00
51ca0a95b5
rephrase tcp.Value methods; add Ring.FreeLimited; work on TxQueue
2025-01-18 09:30:36 -03:00
8b64181167
add TestRingWriteLimited
2025-01-14 07:55:22 -03:00
0a75ef4670
txqueue work
2025-01-13 19:36:17 -03:00
9abf0c11b9
restructure package, rename module/repo
2025-01-07 11:34:35 -03:00
73f0b547b3
add tcp ringtx
2025-01-06 07:15:35 -03:00
17d2987367
add ring buffer implementation
2025-01-05 18:35:56 -03:00
Pat Whittingslow