Let us not forget that the main purpose of such protocol is to enable other users contribute their own client implementations for various languages. Also, most JDBC and ODBC use cases work in thread-per-connection mode.
I think that if we introduce a multi-threaded client here, then it will be a lot harder to understand, configure, use, or contribute, so I agree with Vladimir. Let's keep it simple for now. D. On Wed, Aug 2, 2017 at 10:37 AM, Yakov Zhdanov <yzhda...@apache.org> wrote: > Agree with Alex. I think our implementations should share single connection > over threads in the process. > > --Yakov >
