Github user merlimat commented on the issue:
https://github.com/apache/bookkeeper/pull/126
@eolivelli
> So that in the future we will not forget about this "legacy" option, as
actual is not "legacy" at all if Yahoo/Pulsar is using it in production
I think that for long term we should converge to one single wire protocol
that is both extensible and resource efficient.
BK v2 protocol has its own issues as well (which is why protobuf was
introduced):
* Fixed binary protocol, cannot add new fields and have easy upgrade
* Doesn't have a request id. For example if a client tries to read the
same entry twice, it cannot distinguish the response for each request, thus
needing additional logic in the client to keep track of it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
