Wrong command
If the incoming socket isn't vanilla, we need to use async-read rather than socket-poll (the value of .Available is meaningless)
kill the unsent queue when connection fail; this is far more reasonable (expected), and ensures async works correctly
documentation: pipelines and multiplexers
Typos; contact info; blocking op workaround
Clearer async code
Events documentation
Only prevent sync-continuations if explicitly enabled; otherwise it can cause near-deadlocks in the TPL-pool; avoid a dependency on the thread-pool in SocketManager
damn, wrong state object!
The Dangers of Synchronous Continuations
Fix markdown
Try to detect socket fail in heartbeat
Update KeysValues.md
A suitably evil hack to avoid exec-sync
typo
Test the "deny exec-sync" delegates before trusting them
deny exec-sync: explicitly null the delegates if it throws
clarify names in the exec-sync tests
DenyExecSync can be init-only
Compiles for mono; not saying it works...