my biggest issues with a "standard" wrapper format: 1. _ALL_ client _CODE_ (as opposed to kafka lib version) must be updated to know about the container, because any old naive code trying to directly deserialize its own payload would keel over and die (it needs to know to deserialize a container, and then dig in there for its payload). 2. in order to write middleware-friendly clients that utilize such a container one would basically have to write their own producer/consumer API on top of the open source kafka one. 3. if you were going to go with a wrapper format you really dont need to bother with a kip (just open source your own client stack from #2 above so others could stop re-inventing it)
On Wed, Nov 2, 2016 at 4:25 PM, James Cheng <wushuja...@gmail.com> wrote: > How exactly would this work? Or maybe that's out of scope for this email.
