Re: Writing a client: Connection pooling

2015-05-18 Thread Warren Falk
acting as the consumer > coordinator, etc. Again, this is just the client implementation details, of > how you would like to make use of the protocol guarantees while considering > performance, usability, etc. > > Guozhang > > > On Thu, May 14, 2015 at 3:34 PM, Warren Falk &

Re: Writing a client: Connection pooling

2015-05-14 Thread Warren Falk
> coordinator, etc, and we have also once discussed about using a separate > channel for metadata refresh. > > So I think we should modify the above statement in the wiki. Thanks for > pointing out. > > Guozhang > > On Wed, May 13, 2015 at 7:44 AM, Warren Falk > wrote

Writing a client: Connection pooling

2015-05-13 Thread Warren Falk
I'm working on the C# client. The current Kafka Protocol page says this: "it should not generally be necessary to maintain multiple connections to a single broker from a single client instance (i.e. connection pooling)" But then says this: "The server guarantees that on a single TCP connection,