KafkaReceiver is in need of a cleaner implementation, better internal naming, and documentation. This PR kick starts that effort, since this PR already contains too many changes. All subsequent changes will be isolated in PRs.
KafkaReceivermight get renamed to KafkaSubscriber to match the Publisher name, this can be done while gracefully migrating.
The new threading model of the receiver allows more code to run on the user thread, while guaranteeing that as little as possible code runs on the receiver. It also temporarily added some development utilities to verify the threads during dev/testing.
This PR is the start of the internal clean-up.
KafkaReceiveris in need of a cleaner implementation, better internal naming, and documentation. This PR kick starts that effort, since this PR already contains too many changes. All subsequent changes will be isolated in PRs.KafkaReceivermight get renamed toKafkaSubscriberto match thePublishername, this can be done while gracefully migrating.The new threading model of the receiver allows more code to run on the user thread, while guaranteeing that as little as possible code runs on the receiver. It also temporarily added some development utilities to verify the threads during dev/testing.