[ 
https://issues.apache.org/jira/browse/GEODE-8997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313933#comment-17313933
 ] 

ASF subversion and git services commented on GEODE-8997:
--------------------------------------------------------

Commit ae6b3ac1550bdaed75159fbbe360b6733e7e84ee in geode's branch 
refs/heads/develop from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ae6b3ac ]

GEODE-8997: remove protobuf client server code (#6168)

* GEODE-8997: remove protobuf client server code

This removes the experimental Protobuf-based client/server subproject
and associated files.  Protobuf is no longer included as a Geode dependency.

* updated expected files list in geode-assembly

* removed protobuf-related exceptions from excludedClasses.txt

* exclude service loading exception from serializables test

> remove protobuf client server code
> ----------------------------------
>
>                 Key: GEODE-8997
>                 URL: https://issues.apache.org/jira/browse/GEODE-8997
>             Project: Geode
>          Issue Type: Improvement
>          Components: client/server
>            Reporter: Darrel Schneider
>            Assignee: Bruce J Schuchardt
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> The protobuf based client/server project is essentially dead but code for it 
> is still part of geode.
> This complicates the implementation. For example I was working on an 
> improvement to have the thread monitor detect stuck server connection threads 
> and found myself trying to figure out how to make this work for 
> ProtobufServerConnection.
> I think it would be best to remove the dead protobuf code. I'm not sure what 
> all of it is but here is what I have found so far:
> ProtobufServerConnection
> package org.apache.geode.internal.cache.client.protocol
> package org.apache.geode.internal.protocol.protobuf.v1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to