1. "The new
consumer API is non blocking and instead of returning a blocking iterator,
the consumer provides a poll() API that returns a list of records. "
So this means the consumer polls, and if there are new messages it pulls
them down and then disconnects?
" The consumer also allows long poll
to reduce the end-to-end message latency for low throughput data."
How is this different than blocking? Is it even based meaning it keeps a
long poll conneciton open, and if/when a new message arrives it triggers an
event on the consumer side?
" The consumer batches
data and multiplexes I/O over TCP connections to each of the brokers it
communicates with, for high throughput. "
If it is single threaded, does each tcp brocker connection block? Not sure
I understand how this works if it is single threaded.
On Thu, Feb 27, 2014 at 11:38 PM, Robert Withers <[EMAIL PROTECTED]