Hey Jun,
I think the existing scala clients should just remain as they are. There is
no point updating them, and as you say it would be quite fragile. The
conversion to the new requests would just be for the server usage.
-Jay
On Mon, Feb 9, 2015 at 9:48 AM, Jun Rao wrote:
> We need to be a bi
We need to be a bit careful when doing 2b. Currently, our public apis
include SimpleConsumer, which unfortunately exposes our RPC
requests/responses. Doing 2b would mean api changes to SimpleConsumer. So,
if we want to do 2b before 3, we would need to agree on making such api
changes. Otherwise, 2b
Argh, I just realized that the producer and consumer have already almost
removed that so it wouldn't be in common but just something for the
broker. Maybe later this year 0.9/1.0 item to crack into.
On Sun, Feb 8, 2015 at 11:34 AM, Joe Stein wrote:
> Jay,
>
> Can we add another package (or two)
Jay,
Can we add another package (or two) to org.apache.kafka.common for metadata
and consensus. We can call them something else but the idea would be to
have 1 common layer for meta data information (right now we put the json
into zookeeper) and 1 common layer for asynchronous watches (which we w
Thanks for the background.
I picked the Network classes portion of it, since I was already looking at
how to refactor send/receive and friends to support extending with TLS and
SASL. Having to do this in just one place will be really nice :)
Gwen
On Sun, Feb 8, 2015 at 7:26 AM, Jay Kreps wrote:
