initial TODO

Yeah I always do these...

• Finish renaming some variables

• Retry if lru-crawler busy

• Rest of socket error handling

• Shorten some of the reparsing code

• Rate limiting experiments (currently is none)

• STDOUT mode, for dumping to file or socat/netcat

• Commandline argument for data buffer size (currently 16 megabytes)

• TLS support for destination at least

• Also a performance fix that's a little more involved: if we're stuck waiting for any particular POLL value, but another socket is ready for data, and that data is for a full buffer, it'll keep waking up burning CPU.

• Allow buffering keylist to disk as to not block the LRU crawler for a long period of time, if expiration crawling is critical to a workload.

The issue is a broad checklist covering variable renaming, the LRU crawler, socket error handling, reparsing, STDOUT mode, TLS for the destination, and disk buffering. No files, tests, or single entry point are named; first split the checklist into focused issues, then define completion and validation separately for each item.