I was very excited when the protobuf support became available as it allowed for
the fairly quick development of a Go client.
(https://github.com/gemfire/geode-go-client). As Udo already mentioned,
removing this functionality reduces our potential exposure to new use cases and
language bindings.
I also worked on the protobuf interface for a little while, although not for as
long as some of the other folks commenting. I'm ok with removing it. I do see
some value in leaving stalled/incomplete projects around as bait for future
developers to pick up - that seems to have worked for redis ;)
Thank you, Owen.
My bad. I had forgotten I had added myself also to the "Client/server messaging
and cache operations" sections of the code which explains why I was added as
reviewer to the PRs I did not expect.
Best regards,
Alberto
From: Owen Nichols
Sent: W
Thanks Alberto for the detailed list. I think I was able to find explanations
for all, see below.
> https://github.com/apache/geode/pull/6177
#
geode-core/src/main/java/org/apache/geode/cache/client/internal/QueueManagerImpl.java
#matches your rule:
# geode-core/**/org/apache/geode/cache/client
Hi Owen,
Here are some PRs I feel I was added to in error:
https://github.com/apache/geode/pull/6177
https://github.com/apache/geode/pull/6156
https://github.com/apache/geode/pull/6153
https://github.com/apache/geode/pull/6151
https://github.com/apache/geode/pull/6075
https://github.com/apache/ge
